-bash-3.00# cat /proc/user_beancounters
Version: 2.5
uid resource held maxheld barrier limit failcnt
104: kmemsize 3943800 4160542 9753527 9752512 0
lockedpages 0 0 32 32 0
privvmpages 23222 38193 69152 73575 2
shmpages 2441 3417 8192 8192 0
dummy 0 0 0 0 0
numproc 53 58 256 256 0
physpages 14000 16202 0 2147483647 0
vmguarpages 0 0 6144 2147483647 0
oomguarpages 14004 16202 6144 2147483647 0
numtcpsock 8 12 80 80 0
numflock 4 10 100 110 0
numpty 1 1 16 16 0
numsiginfo 0 3 256 256 0
tcpsndbuf 0 24508 319488 524288 0
tcprcvbuf 0 10116 319488 524288 0
othersockbuf 22280 27124 132096 336896 0
dgramrcvbuf 0 2228 132096 132096 0
numothersock 15 21 80 80 0
dcachesize 237062 270354 1048576 1097728 0
numfile 3239 3501 4086 4086 0
dummy 0 0 0 0 0
dummy 0 0 0 0 0
dummy 0 0 0 0 0
numiptent 10 10 128 128 0
privvmpages is the amount of memory than can be allocated by processes, it does not account memory use
vmguarpages is the memory guaranteed for use, and it is woefully low at 6144 (looks like the default config for pong)
oomguarpages is accounting the actual memory use and you can see it far exceeds vmguarpages
guys plz read up in the wiki on /proc/user_beancounters
AND WARNING! dont take the default config and try to adjust it up for a Java machine because there is zero match to your hardware. use vzsplit 8 or 16 or more ways to discover your hardware capabilities
[Updated on: Mon, 27 August 2007 00:21]
Report message to a moderator