The heap size (-Xmx256m) only controls the Java heap, and does not include other things that are part of the KJS like the DSYNC cache and the appserver C++ infrastructure. As a rule of thumb, I usually suggest that
you should give the KJS room to grow to about twice the size of the heap. (The more heap you have, the larger the amount of infrastructure and cache).
(By the way, are you using the option -Xmx256m or -mx256m? Looks like a possible typo. I don't really know the HP JVM, but the docs say that -Xmx256m is the correct flag.)
So, in your case I'd expect to see the following at steady state:
6 KJS processes @ around 0.5 GB each.
A KXS processes @ around 0.75 GB. This is widely variable, however, based on your session usage.
A bunch of other processes (SLAPD, KAS, etc.) that should remain relatively small in comparison to the KJS and KXS proceses. Total : 0.25-0.5 GB ?
So I wouldn't expect you to need more than 4-5 GB of phyiscal memory for this type of system. You mention that the system is using significantly more memory than that. Where is the memory being used? KJS processes? KXS processes? SLAPD?
David
Edit: 9:01, fixed typo in JVM arguments, grammar
[ September 12, 2002: Message edited by: David Ogren ]