Virtual resource partitioning: Difference between revisions

Revision as of 16:44, 31 July 2009

Latest revision as of 04:50, 27 March 2022

(48 intermediate revisions by 22 users not shown)

Line 1:

{{uncategorizedrefimprove|date=July 2009}}

{{article issues|copyedit=July 2009|expand=July 2009|unreferenced=July 2009}}

'''Virtual Resoruce Partitioning''' (also known as VRP) is a [[virtualization]] tachnology that allows to allocated computerized resources (such as CPU & IO) to transactions.

Unlike'''Virtual conventionalresource virtualization technologiespartitioning''' (such'''VRP''') asis thosean [[operating system-level virtualization]] technology that areallocates usedcomputing byresources (such as [[VmwareCPU]] that& alloicate[[I/O]]) to transactions. Conventional virtualization technologies allocate resources peron operatigan [[operating system]] ([[windowsWindows]], [[Linux]]...), thewide basis. VRP technology is workingworks 2 levellevels deepersdeeper whileby allowing to regulateregulation and control the amount of resorucesthe that areresources used by specific transactions within thean application.<ref>{{

cite conference

VRP technology is used to give more (or less) resources to applicative transaction and by that, boost it (or slow it down).

| last = Lipari| first = G.| last2 = Bini| first2 = E.

| title = Resource partitioning among real-time applications

| book-title = Real-Time Systems, 2003. Proceedings. 15th Euromicro Conference on

| pages = 151–158

| publisher = IEEE Xplore

| date = 2–4 July 2003

| isbn = 0-7695-1936-9| doi = 10.1109/EMRTS.2003.1212738| hdl = 11382/374720

| hdl-access = free

}}</ref>

In many computerized environments, a single user, application, or transaction can appropriate all server resources and by that, affect the quality of service & user experience of other active users, applications or transactions. For example, a single report in a [[data warehouse]] environment can monopolize data access by demanding large amounts of data. Similarly, a CPU-bound application may consume all server processing power and starve other activities.

VRP allows balancing, regulating and manipulating the resource consumption of individual transactions, and by that, improving the overall quality of service, compliance with service level agreements, and the ultimate end user experience.

==Technology overview==

VRP is usually implemented in the OS in a way that is completely transparent to the application or transaction. The technology creates virtual resource "lanes", each of which has access to a controllable amount of resources, and redirects specific transactions to those lanes allowing them to take more or less resources.

VRP can be implemented in any OS and is available on [[Microsoft Windows|Windows]], [[Red Hat]], [[SUSE Linux|Suse]], [[HP-UX]], [[Solaris (operating system)|Solaris]], [[tru64]], [[AIX]] and others.

In any OS, the application communicates with the OS kernel in a specific way which requires a different VRP implementation. A safe implementation of VRP usually combines several resource allocation techniques. VRP implementations depend on rapidly varying transaction type, consumed resource and kernel state. The VRP implementation must adapt to such changes in real-time.

==References==

<references/>

<!-- The material in this ref needs to be incorporated into the article -->

* [http://www.slideshare.net/jimmyschwarzkopf/infrastructure-market-2009 VRP as a new trend in the IT industry]

* [http://www.morevrp.com/resources/about-vrp VRP technical overview as implemented by one of the VRP vendors]

[[Category:Virtualization]]

{{uncategorized|date=July 2009}}