Virtual resource partitioning: Difference between revisions

Revision as of 04:42, 24 April 2014

Latest revision as of 04:50, 27 March 2022

(7 intermediate revisions by 6 users not shown)

Line 1:

{{multiple issuesrefimprove|refimprovedate=July 2009|orphan =April 2010}}

'''Virtual resource partitioning''' ('''VRP''') is an [[operating system-level virtualization]] technology that allocates computing resources (such as [[CPU]] & [[I/O]]) to transactions. Conventional virtualization technologies allocate resources on an [[operating system]] ([[Windows]], [[Linux]]...) wide basis. VRP works 2 levels deeper by allowing regulation and control of the resources used by specific transactions within an application.<ref>{{

Line 5:

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

| title = Resource partitioning among real-time applications

| booktitlebook-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

| url = http://ieeexplore.ieee.org/xpl/freeabs_all.jsp?arnumber=1212738

| hdl-access = free

| isbn = 0-7695-1936-9}}</ref>

}}</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.

Line 19 ⟶ 20:

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 distributions|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.

Line 30 ⟶ 31:

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

[[Category:Virtualization software]]