G1GC

劉俠麟 1245502106 at qq.com
Thu Dec 21 07:35:15 UTC 2023


When using G1GC with jdk11u, I met some cases that g1gc failed to work well and seriously affected the Java application. Here are some details:



With objs promoted to old generation, as well as some humongous objs allocated, the old generation usage exceeds the threshold indicated by IHOP.

G1GC startups concurrent marking.

Concurrent marking is finished, but the Eden is not full and mixed GC can not be triggered.

Humongous objs keep being alllocated and finally cause a to-space exausted.

Eventually, G1 triggers a Full GC for collecting all objs.


I've met plenty of cases which act the same as I described below. I'm confused that it looks like a wrong prediction for old generation growing. Is it fixed in higher JDK version? Or what should I do to deal with such problems. Looking forward to your reply!
Thanks!





劉俠麟
beef.liu at qq.com








劉俠麟
1245502106 at qq.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.openjdk.org/pipermail/hotspot-gc-dev/attachments/20231221/d7c34e49/attachment.htm>


More information about the hotspot-gc-dev mailing list