CPU Fair scheduler - Revision history

Sergey Bronnikov: added category

2015-06-07T06:30:28Z

added category

174.113.196.75 at 00:47, 2 April 2011

2011-04-02T00:47:10Z

174.113.196.75 at 00:46, 2 April 2011

2011-04-02T00:46:43Z

174.113.196.75 at 00:46, 2 April 2011

2011-04-02T00:46:11Z

Grin: stub

2008-05-30T07:56:08Z

stub

New page

The '''Fair scheduler''' distributes CPU resources among the VEs, and controls CPU resource management.

It is a two-level implementation of [[fair-share scheduling]] strategy.

On the first level scheduler decides which VE is give the CPU time slice to, based on per-VE <code>cpuunits</code> values. On the second level the standard Linux scheduler decides which process to run in that container, using standard Linux process priorities and such.

OpenVZ administrator can set up different values of <code>cpuunits</code> for different containers, and the CPU time will be given to those proportionally.

Also there is a way to limit CPU time, e.g. say that this container is limited to, say, 10% of CPU time available.

''...Stay tuned for more info...''

== Monitoring ==
The scheduler can be monitored by using the <code>/proc/vz/[[vestat]]</code> file.

← Older revision		Revision as of 06:30, 7 June 2015
Line 13:		Line 13:
	== Monitoring ==		== Monitoring ==
	The scheduler can be monitored by using the <code>/proc/vz/[[vestat]]</code> file.		The scheduler can be monitored by using the <code>/proc/vz/[[vestat]]</code> file.
		+
		+	[[Category:Definitions‏‎]]

@@ Line 5: / Line 5: @@
 On the first level the scheduler decides which VE to give CPU time slice to, based on per-VE <code>cpuunits</code> values. On the second level the standard Linux scheduler decides which process to run in that container, using standard Linux process priorities and such.
-OpenVZ administrator can set up different values of <code>cpuunits</code> for different containers, and the CPU time will be given to those proportionally.
+The OpenVZ administrator can set up different values of <code>cpuunits</code> for different containers, and the CPU time will be given to those proportionally.
 Also there is a way to limit CPU time, e.g. say that this container is limited to, say, 10% of CPU time available.

@@ Line 3: / Line 3: @@
 It is a two-level implementation of [[fair-share scheduling]] strategy.
-On the first level the scheduler decides which VE is give the CPU time slice to, based on per-VE <code>cpuunits</code> values. On the second level the standard Linux scheduler decides which process to run in that container, using standard Linux process priorities and such.
+On the first level the scheduler decides which VE to give CPU time slice to, based on per-VE <code>cpuunits</code> values. On the second level the standard Linux scheduler decides which process to run in that container, using standard Linux process priorities and such.
 OpenVZ administrator can set up different values of <code>cpuunits</code> for different containers, and the CPU time will be given to those proportionally.