Young GC pause time definitions
Christian
chsu79 at gmail.com
Mon Aug 22 08:54:52 PDT 2011
Sorry for my silence, I have been meaning to come back to this thread
first when I had new information of value to report. (I'll move this
discussion to hotspot-gc-use.)
The bug that was fixed in 6u19 was causing some of the increased GC
times that I could see. Upgrading the jdk did improve the situation. I
don't have exact numbers.
It would be interesting to learn how you guys with good insight to the
details of the GC would use publicly available flags to get
information that break down what the GC is spending time on. I'm
going to be able to have remote access to their lab environment for
some time at which point I could try experiments, and extract
information from gc debug output. PrintTenuringDistribution is
definitely something I want to enable because I'm curious about the
survival rate.
On Mon, Aug 22, 2011 at 17:08, Charles K Pepperdine <kirk at kodewerk.com> wrote:
>>
>>
>> The customer site is running an old jdk 1.6.0_14, with
>> -XX:+UseParNewGC and -XX:UseConcMarkSweepGC. Uses a 12 G heap, a
>> relatively small 512Mb new size.
>
> This seems like a highly suspicious configuration that I would guess is at the root of the problem. Please use -XX:+PrintTenuringDistribution and post the gc log if you can.
>
> Regards,
> Kirk Pepperdine
>
>
More information about the hotspot-gc-use
mailing list