<div dir="ltr"><div dir="ltr">On Wed, Feb 12, 2025 at 3:42 PM <<a href="mailto:ioi.lam@oracle.com">ioi.lam@oracle.com</a>> wrote:</div><div class="gmail_quote gmail_quote_container"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><u></u>
<div>
<p>Hi Charlie,</p>
<p>Thanks for trying CDS out. Is there any performance numbers you
can share with us?</p></div></blockquote><div>Sure! Here's a few JRuby command lines before and after with JDK 21 CDS:</div><div><br></div><div>Hello world, with and without --dev flag (--dev limits to tier 1, disables JRuby JIT):</div><div><br></div><div>jruby -e 1 2.52s user 0.13s system 183% cpu 1.447 total</div><div>jruby --dev -e 1 1.16s user 0.12s system 125% cpu 1.014 total</div><div><br></div><div>With CDS:</div><div><br></div><div>jruby -e 1 1.78s user 0.10s system 192% cpu 0.979 total</div><div>jruby --dev -e 1 0.92s user 0.09s system 120% cpu 0.834 total</div><div><br></div><div>List all installed libraries (gems):</div><div><br></div><div>jruby -S gem list > /dev/null 5.24s user 0.23s system 215% cpu 2.532 total</div><div>jruby --dev -S gem list > /dev/null 2.15s user 0.21s system 112% cpu 2.089 total</div><div><br></div><div>With CDS:</div><div><br></div><div>jruby -S gem list > /dev/null 4.39s user 0.20s system 225% cpu 2.036 total</div><div>jruby --dev -S gem list > /dev/null 1.76s user 0.13s system 131% cpu 1.437 total</div><div><br></div><div>List all build targets in current project (rake):</div><div><br></div><div>jruby -S rake -T > /dev/null 4.58s user 0.25s system 143% cpu 3.363 total</div><div>jruby --dev -S rake -T > /dev/null 1.99s user 0.20s system 81% cpu 2.682 total</div><div><br></div><div>With CDS:</div><div><br></div><div>jruby -S rake -T > /dev/null 3.97s user 0.23s system 141% cpu 2.977 total</div><div>jruby --dev -S rake -T > /dev/null 1.77s user 0.18s system 78% cpu 2.476 total</div><div><br></div><div>The CDS improvements are comparable on their own to --dev, which is great, and combining them with --dev is even more impressive. The CRuby numbers are still 10x faster, but this is getting into a range where the difference is tolerable.</div><div><br></div><div>I'm hoping AOTCache can help us eliminate the need for --dev. Tier 2 code is still much slower than tier 1 code. </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div>
<p></p>
<p></p>
<div>On 2/12/25 10:37 AM, Charles Oliver
Nutter wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">
<div>* OMG that warning output... is there any way to capture
that to a file without redirecting the whole process?</div>
<div>* Why is it not possible to boot with one JSA and then dump
a new JSA at the end? It complains if I use both
SharedArchiveFile and ArchiveClassesAtExit in the same command
line.</div>
</div>
</blockquote>
<p><br>
</p>
<p>That's something we are talking about in the Leyden project -
train with an existing cache and write an updated cache at the
end. What kinds of scenarios are you looking at?<br></p></div></blockquote><div>My interest right now is entirely startup time, which is honestly the only reason JRuby hasn't seem more success in Ruby shops. When we take 10x longer to start up small commands, people just walk away.</div><div><br></div><div>Longer term, we are interested in pre-training the AOT cache specific to a user's application, suitable for deploying a hotter image to a server. I have also been exploring CRaC for that, but it has serious limitations.</div><div><br></div><div>We are looking forward to a future where we can precompile all of the Ruby standard library to JRuby .class output and have it boot up with cached AOT for whatever you happen to use during your command. We're also planning to start pre-generating CDS stuff when publishing container images for e.g. Docker.</div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div>
<p>Have you tried the -XX:+AutoCreateSharedArchive flag? It should
recreate the dynamic archive if you have updated the app's JAR
files or updated to a new JDK.<br></p></div></blockquote><div>This is definitely what we want for the JRuby launcher! I've integrated it into the launcher and it seems to work well (my log redirects must still be included to silence CDS warnings, though):</div><div><br></div>$ rm -f lib/jruby.jsa<br>$ time bin/jruby.sh -e 1<br>bin/jruby.sh -e 1 2.90s user 0.22s system 139% cpu 2.230 total<br>$ time bin/jruby.sh -e 1<br>bin/jruby.sh -e 1 1.79s user 0.11s system 176% cpu 1.081 total<br>$ ls -l lib/jruby.jsa<br><div>-r--r--r-- 1 headius staff 32489472 Feb 12 16:14 lib/jruby.jsa </div><div><br></div><div>I'm keen to play with the preview of AOTCache in 24. If anyone else wants to try this stuff with JRuby, building JRuby is just "clone repo" and then "run ./mvnw". The launcher is bin/jruby at that point and it's just POSIX shell.<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div><blockquote type="cite"><div dir="ltr"><div><div dir="ltr" class="gmail_signature"><div dir="ltr"><div>
</div>
</div>
</div>
</div>
</div>
</blockquote>
</div>
</blockquote></div></div>