|
Re: Help with calculating fair allocations [message #7935 is a reply to message #7922] |
Tue, 31 October 2006 06:39 |
Vasily Tarasov
Messages: 1345 Registered: January 2006
|
Senior Member |
|
|
Hello,
you wrote:
Quote: |
So..if we consider:
Example "C"-248MB RAM --kmemsize 16384000:18022400
What would:
"A"-62MB RAM --kmemsize ?
"B"-124MB RAM --Kmemsize ?
and a monster:
Example "D" -496MB RAM --Kmemsize ?
|
kmemsize parameter is measured in bytes, as all parameters, which name is terminated by ...size.
So if you want to set kmemsize limit to 248MB, limit/barrier should equal 248 * 1024 * 1024 = 260046848. I suppose you'll be able to calculate appropriate numbers for 62/124/496MB.
Also, I would like to add, that kmemsize is not RAM. To get full information on user beancountes (UBC) visit this page and read detailed information about all parameters: http://wiki.openvz.org/UBC.
Sorry, if I misunderstood you.
HTH,
vass.
[Updated on: Tue, 31 October 2006 06:39] Report message to a moderator
|
|
|
|
|
|
Re: Help with calculating fair allocations [message #7954 is a reply to message #7949] |
Tue, 31 October 2006 15:13 |
|
Bryan,
I suggest you to read all the wiki pages about UBCs, dedicating at least a couple of hours for this task. Those pages do have something to say. Especially, please read the description of individual parameters, also wiki: UBC systemwide configuration, and generally all the other UBC-related articles.
vmguarpages is NOT RAM limit. It is a _guarantee_ for allocations.
privvmpages is NOT RAM limit. It is a limit of how many pages a VE can _allocate_ (using, say, malloc()), but not yet use -- as it often happens. The thing is, pages are allocated by applications, but not all of them are used, and in Linux (and any other modern OS), allocation does not yet leads to a page allocated in RAM. In fact, page in RAM is allocated later, when it's used for the first time, and _only_ if it's used. Also, some pages are swapped out.
Again, please read all those articles first, and ask your questions only after you read and undestood that stuff.
Regards,
Kir.
Kir Kolyshkin
|
|
|