Erratic(?) CMS behaviour every 5d

Bernd Eckenfels bernd.eckenfels at googlemail.com
Tue Oct 2 20:43:11 PDT 2012


Hello,



On Fri, Sep 28, 2012 at 7:48 PM, Bernd Eckenfels
<bernd.eckenfels at googlemail.com> wrote:
> The jstat utility has a -gccause option, do you think that will help
> me as soon as the system gets into the trashing mode?

I am currently seeing only "CMS Initial Mark" and "CMS Final Remark"
as causes for OGC and "GCLocker" as cause for ParNew, so I think that
jstat will not help me later on, when the machine starts to go wild
again. The PrintCMSStatistics=2 was not helping me to get to the root.
I will play around with PrintCMSInitiationStatistics but I really
think the GC causes (which statistic was over what limit) should be
more prominently available.

Regarding my "problem": I do see a minor growth in the PGU, so I guess
this is the reason. My fist step was to resize the PG and later on
some heapdumping to find the class loader leak is in order.

Bernd


More information about the hotspot-gc-use mailing list