Editing CPU Fair scheduler

Jump to: navigation, search

Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision Your text
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.
 
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.
  
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.
+
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.  
 
Also there is a way to limit CPU time, e.g. say that this container is limited to, say, 10% of CPU time available.  

Please note that all contributions to OpenVZ Virtuozzo Containers Wiki may be edited, altered, or removed by other contributors. If you don't want your writing to be edited mercilessly, then don't submit it here.
If you are going to add external links to an article, read the External links policy first!

To edit this page, please answer the question that appears below (more info):

Cancel Editing help (opens in new window)