Have to grabbed periodic snapshots with ps, or prstat?
These will gave you a sense of which processes have
large physical memory footprints, and you can pmap
from there....
Thanks,
/jim
Simon wrote:
Hi Jim,
In order to be sure, you need to so some additional memory
accounting and determine how much RAM you need to support
the shared segments for Sybase, and the JVMs.
It's difficult for me now since I don't kwow what is the really
troublemaker to cause this issue,I guess the JVMs,and I will suggest
reduce the share memory allocation for sybase,that control it in
sybase configuration file,not in "/etc/system".
Thanks.
Best Regards,
Simon
On Sun, Nov 22, 2009 at 11:33 AM, Jim Mauro <james.ma...@sun.com
<mailto:james.ma...@sun.com>> wrote:
You have about 9GB of shared memory (on a 16GB machine).
From the "prstat" output,we found 3 sybase process,and each
process derived 12 threads,the java process(launched by
customer application) derived total 370 threads, I think it's
too many threads(especially of "java" program) that generate
excessive stack/heaps,and finally used up the RAM ?
Java can consume a lot of memory. Need to see the memory sizes,
but it's certainly a possibility.
So I think decrease the share memory used by sybase(defined at
sybase configuration layer,not in "/etc/system" file) would be
helpful ?
Sure. If you take memory away from one consumer, it leaves
more for the others. Whether or not it actually solves your
problem, meaning after such a change the system has sufficient
memory to run without paging, remains to be seen.
In order to be sure, you need to so some additional memory
accounting and determine how much RAM you need to support
the shared segments for Sybase, and the JVMs.
Thanks,
/jim
_______________________________________________
dtrace-discuss mailing list
dtrace-discuss@opensolaris.org
