Well, my colleague Rob v.d. Heij beat me to the punch line, but this was
where I was headed....having more than one JVM inside a Linux guest is,
imho, asking for trouble. Is there a reason you need to have multiple
JVMs running at the same time?
Rob van der Heij wrote:
On 10/22/07, Marcy Cortes <[EMAIL PROTECTED]> wrote:
Why would a server show such a high amount in cached when it is needing
to swap?
In your case, it's probably the JVM heap that is resisting. The JVM
does its own management of the heap. Just like in real life: when you
have multiple managers, you want at most one of them to actually do
something ;-) Once the heap has been given to the JVM, Linux memory
management can not see inside. When Linux cannot manage it, you want
the heap to be resident in the virtual machine.
But one can and should question whether the JVM heap is properly
sized. Some of the rules of thumb in sizing the heap (like "when in
doubt, double it") come from the world of spare memory and may not
apply to Linux on z/VM. The Java Garbage Collector is not as scary as
it used to be. There's options in GC to see high water marks etc that
help you size the heap. I have seen installations so oversize that
after weeks the first GC had not even happened. If you can make it
clean up now and then, you limit the amount of fresh pages and have
more chance to keep those pages resident on VM. That may very well
outweigh the extra cost for GC now and then.
Rob
--
Rob van der Heij
Velocity Software, Inc
http://velocitysoftware.com/
--
DJ
V/Soft
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
