Start by enabling GC logging and then analyse the log to see what it is doing during GC.
On Thursday, 21 December 2017 17:25:09 UTC, Abhishek Agarwal wrote: > > Hello everyone, > Recently, I had one of the JVMs going into this weird state wherein minor > gc start kicking almost every minute but what is most surprising that it is > one minor GC is taking as much as 100 seconds. The heap size is around 12 > gigs and young gen is about 30% of that. As soon as gc starts, > understandably CPU usage started increasing as well. I am not able to > figure out how would one minor GC take this much time. The machine does not > have swapping enabled. I also ran sar and confirmed there was no swapping > during the issue. We are using parallel GC for young gen and CMS for old > gen GC. How can I go about troubleshooting this further? Any pointers will > be appreciated. > -- You received this message because you are subscribed to the Google Groups "mechanical-sympathy" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
