search

mdzidic / ovz-web-panel

Automatically exported from code.google.com/p/ovz-web-panel
Other
0 stars 0 forks source link

Ability set guaranteed RAM, burstable RAM and swap space #127

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Reason: It would be nice to have and option to set the amount of guaranteed and 
burstable ram for a container and also swappages

Description: http://wiki.openvz.org/UBC_parameters_table

Original issue reported on code.google.com by alecksie...@gmail.com on 3 Jul 2010 at 8:10

GoogleCodeExporter commented 9 years ago 
dependant on rhel5 kernel 028stab060.2 or debian backports kernel 2.6.32-bpo.5
also vzctl > 3.0.24 is needed.

Original comment by dvdo...@chello.nl on 6 Jul 2010 at 2:44

GoogleCodeExporter commented 9 years ago 
Please explain what do you mean under "guaranteed and bustable ram"? 
privvmpages parameter? It's possible to set this limit using panel. But for 
simplification panel forces to set limit and barrier number to the same value. 

As for swappages rhel5 kernel and new vzctl are required.

Original comment by sibprogrammer on 6 Jul 2010 at 2:56

GoogleCodeExporter commented 9 years ago 
Simple, for RAM set the barrier (guaranteed) and limit (burst). It's somewhat 
related to issue 178...

Original comment by alecksie...@gmail.com on 2 Oct 2010 at 9:31

GoogleCodeExporter commented 9 years ago 
Ok, I got it.

Original comment by sibprogrammer on 2 Oct 2010 at 4:04

GoogleCodeExporter commented 9 years ago

Original comment by sibprogrammer on 7 Nov 2010 at 4:21

GoogleCodeExporter commented 9 years ago

Original comment by sibprogrammer on 17 Apr 2011 at 12:46

GoogleCodeExporter commented 9 years ago

Original comment by sibprogrammer on 1 May 2012 at 2:52

GoogleCodeExporter commented 9 years ago 
If you still set privvmpages barrier and limit to same value, it's a major bug.

From UBC docs (http://wiki.openvz.org/Privvmpages#privvmpages):

There should be a safety gap between the barrier and the limit for privvmpages 
parameter to reduce the number of memory allocation failures that the 
application is unable to handle. This gap will be used for “high-priority” 
memory allocations, such as process stack expansion. Normal priority 
allocations will fail when the barrier of privvmpages is reached.

Original comment by kolysh...@gmail.com on 13 Jun 2012 at 6:38

GoogleCodeExporter commented 9 years ago 
SWAP is needing:

http://wiki.openvz.org/VSwap

Original comment by cod...@iscgr.de on 11 Dec 2012 at 9:39

GoogleCodeExporter commented 9 years ago 
Issue 389 contains a better description.

Original comment by sibprogrammer on 2 Feb 2013 at 9:46