Difference between revisions of "Resource management"
(wtf... while i'm at it, just go ballistic and fix everything i can without learning what you are talking about first :)) |
(updated) |
||
(6 intermediate revisions by 4 users not shown) | |||
Line 1: | Line 1: | ||
− | '''OpenVZ resource management''' is a set of controls providing per-[[ | + | '''OpenVZ resource management''' is a set of controls providing per-[[container]] resource accounting and limiting. This is required for multiple containers to coexist gracefully on a single [[host system]]. |
− | OpenVZ resource management includes these primary controllers: | + | OpenVZ resource management includes these four primary controllers: |
− | * [[User beancounters]] | + | * [[User beancounters]] (and [[VSwap]]) |
− | * [[ | + | * [[Disk quota]] |
− | * [[CPU | + | * [[CPU Fair scheduler]] |
+ | * [[I/O priorities]] and [[I/O limits]] | ||
+ | |||
+ | OpenVZ administrators can also use the following mainstream Linux mechanisms: | ||
+ | * [[Traffic accounting with iptables]] | ||
* [[Traffic shaping with tc]] | * [[Traffic shaping with tc]] | ||
− | + | [[Category:Resource management]] | |
− | |||
− | |||
[[Category:Definitions]] | [[Category:Definitions]] | ||
[[Category:Kernel]] | [[Category:Kernel]] |
Latest revision as of 11:10, 13 December 2013
OpenVZ resource management is a set of controls providing per-container resource accounting and limiting. This is required for multiple containers to coexist gracefully on a single host system.
OpenVZ resource management includes these four primary controllers:
OpenVZ administrators can also use the following mainstream Linux mechanisms: