<!DOCTYPE html><html><head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body>
<p>On 8/27/24 5:04 AM, Ravi wrote:</p>
<blockquote type="cite" cite="mid:CANxHB3RqES+DqqKcJw4Nc+7d9ecG6B5xGROciA8MOqP_8aFf=A@mail.gmail.com">
<div dir="ltr">Dear Experts,
<div><br>
</div>
<div>We have an application running on jre <span style="color:black;font-family:Calibri,sans-serif;font-size:11pt">1.8u261
with the below jvm arguments:</span></div>
<div><span style="font-size:11pt;line-height:107%;font-family:Calibri,sans-serif"> -Xms8g
-Xmx8g -XX:MetaspaceSize=2g -XX:MaxMetaspaceSize=2g
-XX:+UseG1GC -XX:ParallelGCThreads=2
-XX:ConcGCThreads=1 -XX:+PrintFlagsFinal</span><span style="color:black;font-family:Calibri,sans-serif;font-size:11pt"><br>
</span></div>
<div><span style="font-size:11pt;line-height:107%;font-family:Calibri,sans-serif"><br>
</span></div>
<div><span style="font-size:11pt;line-height:107%;font-family:Calibri,sans-serif">From
the jfrs, we could see Humongous allocation failures are
happening in the G1New and aswell G1Old spaces:</span></div>
</div>
</blockquote>
<p>I think humongous allocation failure will first attempt a young
collection.<br>
This may free regions, potentially resulting in a sequence of free
regions<br>
sufficient to satisfy the humongous allocation request. Only if
that fails is<br>
a full collection performed. That seems to be what your trace
shows, e.g. a<br>
fill (G1Old) collection occurring shortly after the young (G1New)
collection<br>
in each case.<br>
<br>
</p>
</body>
</html>