Re: How is the privvmpages limit reached? [message #27104 is a reply to message #27101] |
Sat, 09 February 2008 16:48 |
rickb
Messages: 368 Registered: October 2006
|
Senior Member |
|
|
Hi, it sounds like you have been reading webhostingtalk for technical information. not a good idea..
jre is known for allocating _far_ more memory then it needs. due to this, your privvmpages will be much higher then physpages. other applications such as bind exhibit this as well. this is why you will never see privvmpages.limit=vmguarpages.limit
@@@
privvm=188389
phys=40864
In this case, your apps are allocating X amounts of memory and using X/4 to store data in it. There is no way to correct this in openvz; you should provide an adequate privvmpages limit for your application's hunger. Privvmpages is not a "burst" memory in the true sense, as your applications cannot realistically store 196608 pages (your limit) of data in memory. but, a high privvmpages on a non overcommitted hardware node can allow overuse of your vmguarpages.limit, which is a memory burst. the amount of burstable memory is difficult to report, rather you can report the memory allocation burst. the non vz linux kernel allows you to allocate as much memory as you wish, which is why your xen environment does not have this problem.
Quote: | Someone said to me "OpenVZ does offer SLM like propoerties in reporting RAM so you should be ok with day to day usage of it rather than the old method where is reported the RAM of the host"
|
there are 2 sources for memory reporting- proc/meminfo and proc/user_beancounters. the most accurate source is always user_beancounters.
Quote: | And the "free" command also shows a total RAM of the VPS and not that of the host
|
read the vzctl man page for the 'meminfo' option; it is possible to customize proc/meminfo reporting.
Cheers
Rick
-------------
Common Terms I post with: http://wiki.openvz.org/Category:Definitions
UBC. Learn it, love it, live it: http://wiki.openvz.org/Proc/user_beancounters
[Updated on: Sun, 10 February 2008 02:57] Report message to a moderator
|
|
|