Profile Image
Reiner Saddey

Strange recommendation when using Shenandoah

Our analysis tells that your application is suffering from long running GC events. 331 GC events took more than 5.0 seconds. Long running GCs are unfavourable for application's performance.
Read our recommendations to reduce long GC pause

 

However within the same report, the max. pause time is 914 ms - who's lying?

 

Any chance gceasy is mixing-up pause and concurrent times?



Report URL - https://gceasy.io/my-gc-report.jsp?p=c2hhcmVkLzIwMjEvMDcvMjYvLS1nYy0yMDIxLTA3LTI0XzIzLTU5LTE5LmxvZy0tMjAtNDQtNTc=&channel=WEB

  • shenandoah

  • gcevents

  • pausetime

  • concurenttime

Please Sign In or to post your comment or answer

Profile Image

Ram Lakshmanan

Hello Reiner!

 

 Greetings.

 

 Apologies. You are right, in this case tool is mixing up concurrent GC time and stop-the-world time and reporting it. Your max pause time is only 914ms. It's evident from the GC Pause duration time graph. 

 

 

 We will fix this issue shortly. Thank you.

 

Got something else on mind? Post Your Question

Not the answer you're looking for? Browse other questions tagged

  • shenandoah

  • gcevents

  • pausetime

  • concurenttime

Edit your question

Separate with comma, space or ENTER key. Special characters are not allowed in tag.

Edit your Answer

Edit your Comment