Re: vmguarpages != oomguarpages ? [message #37453 is a reply to message #37398] |
Fri, 11 September 2009 15:45  |
maratrus
Messages: 1495 Registered: August 2007 Location: Moscow
|
Senior Member |
|
|
Hello Niki,
sorry but I really couldn't catch you.
If you don't mind I'd rather not pass through each of your logical steps.
I just want to pay my attention to
Quote: |
Is there a good reason to set oomguarpages to 100 MB and vmguarpages to 120 MB in my hypothetical example?
|
Please keep in mind the following statement which is taken from\
http://wiki.openvz.org/Privvmpages#oomguarpages
Quote: |
The total out-of-memory guarantees given to the containers should not exceed the physical capacity of the computer, as discussed in UBC systemwide configuration#Memory and swap space. If guarantees are given for more than the system has, in out-of-memory situations applications in containers with guaranteed level of service and system daemons may be killed.
|
http://wiki.openvz.org/UBC_systemwide_configuration#Memory_a nd_swap_space
Quote: |
Commitment levels more than 1 means that the containers are guaranteed more memory than the system has. Such overcommitment is strongly not recommended, because in that case if all the memory is consumed, random applications, including the ones belonging to the host system, may be killed and the system may become inaccessible by ssh(1) and lose other important functionality.
|
Use the formula (or vzcfgvalidate utility) to make sure that Commitment level doesn't exceed 1.
|
|
|