MXBeans to report pause times seem to indicate the complete GC cycle time

Aleksey Shipilev shade at redhat.com
Thu Apr 12 19:52:54 UTC 2018


On 04/11/2018 04:31 PM, Aleksey Shipilev wrote:
> On 04/04/2018 04:56 PM, Viton, Pedro (Nokia - ES/Madrid) wrote:
>> I think that Shenandoah GC should only report in the MXBean the time it has paused the Java
>> application, in the same way it is done with G1 and CMS+ParNew, and not the whole processing time
>> (pause + concurrent time)
> 
> Thanks for the report! This makes sense. Zhengyu is going to look into this.

Zhengyu pushed the fix to sh/jdk:
  http://hg.openjdk.java.net/shenandoah/jdk/rev/040b0d8b5f24

It would take a while for the fix to propagate to backports and RPMs. You may want to pick up the
latest binary build for sh/jdk, and see if it does what you suggested. Builds b57 and later here
have the fix:
  https://builds.shipilev.net/openjdk-shenandoah-jdk/

Thanks,
-Aleksey


More information about the shenandoah-dev mailing list