OpenVZ Forum: Support » Hitting the privvmpages limit

Home » General » Support » Hitting the privvmpages limit

Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend

Hitting the privvmpages limit [message #33462]

Wed, 15 October 2008 13:37

John Kelly
Messages: 97
Registered: May 2006
Location: Palmetto State

Member

Comapring openvz vs. xen, hitting the privvmpages limit is a serious disadvantage of openvz. Even with a generous plan at many providers, you still risk hitting the limit.

Is there any kernel work planned or in progress to integrate container memeory with swap, so that virtual memory allocation works more like a standard kernel with swap?

?

[Updated on: Wed, 15 October 2008 13:40]

Report message to a moderator

Re: Hitting the privvmpages limit [message #33463 is a reply to message #33462]

Wed, 15 October 2008 13:56

maratrus
Messages: 1495
Registered: August 2007
Location: Moscow

Senior Member

Quote:

Comapring openvz vs. xen, hitting the privvmpages limit is a serious disadvantage of openvz. Even with a generous plan at many providers, you still risk hitting the limit.

1. privvmpages are not equal ro RAM pages.
2. privvmpages are equal to virtual pages.
3. virtual pages are equal to RAM + SWAP.

So, increasing privvmpages increase RAM+SWAP consumption of the VE.
Thus in can be concluded that current OpenVZ doesn't distinguish RAM and SWAP from inside the VE.

Quote:

Is there any kernel work planned or in progress to integrate container memeory with swap, so that virtual memory allocation works more like a standard kernel with swap?

Yes, of course. The development of such behavior is in progress.

Report message to a moderator

Re: Hitting the privvmpages limit [message #33468 is a reply to message #33463]

Wed, 15 October 2008 15:11

John Kelly
Messages: 97
Registered: May 2006
Location: Palmetto State

Member

maratrus wrote on Wed, 15 October 2008 09:56

2. privvmpages are equal to virtual pages.

Yes, but the problem is, many applications allocate virtual memory they never use. There may be enough real memory to run the app, but because they preallocate a large request of virtual memory for later use, they fail.

Quote

Is there any kernel work planned or in progress to integrate container memeory with swap, so that virtual memory allocation works more like a standard kernel with swap?

Yes, of course. The development of such behavior is in progress.

I believe that should be one of the highest priorities for openvz development. It will make openvz much more appealing.

Cool

Report message to a moderator

Re: Hitting the privvmpages limit [message #33485 is a reply to message #33468]

Thu, 16 October 2008 10:39

khorenko
Messages: 533
Registered: January 2006
Location: Moscow, Russia

Senior Member

Quote:

i guess this situation can be easily workarounded by increasing privvmpages limits, right? Smile

If your problem is solved - please, report it!
It's even more important than reporting the problem itself...

Report message to a moderator

Re: Hitting the privvmpages limit [message #33486 is a reply to message #33485]

Thu, 16 October 2008 12:37

John Kelly
Messages: 97
Registered: May 2006
Location: Palmetto State

Member

finist wrote on Thu, 16 October 2008 06:39

i guess this situation can be easily workarounded by increasing privvmpages limits, right? Smile

No, not when you're paying for a plan at a provider. If your answer is to pay more for a higher plan, then I'll switch to a xen provider and get more value for the same money.

If you don't want to improve openvz, users will seek alternatives.

[Updated on: Thu, 16 October 2008 12:40]

Report message to a moderator

Previous Topic:	kernel-devel 2.6.24-ovz006.2.
Next Topic:	Maximum Execution

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Sun Aug 11 14:11:12 GMT 2024

Total time taken to generate the page: 0.03013 seconds