When I run the application instrumented with yjp, a Full GC cycle
occurs just after each minor collection.
Is yjp doing this purposefully?
Why? Trying to reduce the memory footprint of any snapshots?
Thanks!
Martin
EA612: Full Garbage collection at each minor collection
-
- Posts: 17
- Joined: Mon May 16, 2005 8:40 pm
-
- Posts: 6172
- Joined: Wed Aug 11, 2004 8:37 am
-
- Posts: 17
- Joined: Mon May 16, 2005 8:40 pm
-
- Posts: 6172
- Joined: Wed Aug 11, 2004 8:37 am
-
- Posts: 17
- Joined: Mon May 16, 2005 8:40 pm
1.5.0_03 - Sparc 64-bit installed - running 32 bit.
The interval appears to be exactly 60s (plus the GC time),
and there's always a minor colletion followed by a full collection.
Under more load, additional minor collection are occurring.
From telemetry point of view, this is fairly convenient, as I
can look at the old generation and get to see the current state
at fixed measurement intervals.
It would be good to make such a feasure optional though.
The interval appears to be exactly 60s (plus the GC time),
and there's always a minor colletion followed by a full collection.
Under more load, additional minor collection are occurring.
From telemetry point of view, this is fairly convenient, as I
can look at the old generation and get to see the current state
at fixed measurement intervals.
It would be good to make such a feasure optional though.
-
- Posts: 6172
- Joined: Wed Aug 11, 2004 8:37 am