CMS: "premature" minor GCs w/ ParNew

Thomas Schatzl thomas.schatzl at
Wed May 15 17:30:05 UTC 2013


  forget that last message, I was looking at a similar issue lately with
G1, but this is ParNew/CMS.

The options I suggested are G1 options.


On Wed, 2013-05-15 at 19:27 +0200, Thomas Schatzl wrote:
> Hi,
> On Wed, 2013-05-15 at 09:58 -0700, Srinivas Ramakrishna wrote:
> > Does it happen with a specific application?
> > 
> > You might want to print the gc cause and see. It could be related to
> > allocating very large objects (arrays). +PrintGCDetails and
> > +PrintHeapAtGC would provide additional data (but probably not the
> > cause, although that may have changed in more recent builds (JDK
> > 8/hs25+? have lost track..)
> You can use -XX:+UnlockDiagnosticVMOptions -XX:G1LogLevel=finest to get
> most detail. PrintGCDetail by maps to G1LogLevel=finer or so (one level
> coarser) iirc.
> Thomas

More information about the hotspot-gc-dev mailing list