<!DOCTYPE html><html><head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body>
<p>Thanks again Ioannis, all this is very good empirical evidence
which should be helpful in zeroing in on a possible inlining
improvement for the kind of code shapes associated with FFM.</p>
<p>Cheers<br>
Maurizio<br>
</p>
<div class="moz-cite-prefix">On 23/11/2024 12:20, Ioannis Tsakpinis
wrote:<br>
</div>
<blockquote type="cite" cite="mid:CAL=VLdUUv6-BKVmnUrsLX_B-bPOrXg7Jvyz872A7RoCvKDWWUw@mail.gmail.com">
<pre>With: -XX:-ClipInlining
245 call-sites with eliminated allocations
0 DesiredMethodLimit failures
353 NodeCountInliningCutoff failures
With: -XX:-ClipInlining -XX:+StressIncrementalInlining
394 call-sites with eliminated allocations
0 DesiredMethodLimit failures
2 NodeCountInliningCutoff failures
Performance baseline:
---------
duration: 2.381 seconds
duration: 2.127 seconds
duration: 2.124 seconds
duration: 2.108 seconds
duration: 2.101 seconds
duration: 2.076 seconds
duration: 2.056 seconds
duration: 2.086 seconds
duration: 2.055 seconds
duration: 2.041 seconds
Performance with -XX:-ClipInlining -XX:+StressIncrementalInlining:
---------
duration: 2.572 seconds
duration: 2.248 seconds
duration: 2.175 seconds
duration: 2.082 seconds
duration: 1.995 seconds
duration: 1.919 seconds
duration: 1.878 seconds
duration: 1.895 seconds
duration: 1.87 seconds
duration: 1.902 seconds
</pre>
</blockquote>
</body>
</html>