Degenerated GC pauses for 5-10 seconds
Aleksey Shipilev
shade at redhat.com
Fri Jan 18 17:11:26 UTC 2019
On 1/18/19 6:02 PM, Alexander Yakushev wrote:
> Look around ShenandoahAllocationTrace and ShenandoahAllocationTraceThreshold. It would print
> warnings to GC log if stalls are detected. You can also employ a nuclear option: set
> ShenandoahPacingDelay=${HUGE_VAL}, for example 30000. Then you should never Degen/Full GC, and
> instead block the allocating thread waiting for GC to complete.
>
>
> I couldn't find any info on ShenandoahAllocationTraceThreshold. What should it be set to?
My bad, wrong option name, this one:
diagnostic(intx, ShenandoahAllocationStallThreshold, 10000, \
"When allocation tracing is enabled, the allocation stalls " \
"larger than this threshold would be reported as warnings. " \
"Time is in microseconds.") \
-Aleksey
More information about the shenandoah-dev
mailing list