<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>performance on Paul Piper</title><link>https://www.paul-piper.de/tags/performance/</link><description>Recent content in performance on Paul Piper</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><copyright>©Paul Piper</copyright><lastBuildDate>Mon, 05 Oct 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://www.paul-piper.de/tags/performance/index.xml" rel="self" type="application/rss+xml"/><item><title>The JVM Taught Us Tiered Compilation</title><link>https://www.paul-piper.de/posts/tiered-compilation-jvm-vs-julia/</link><pubDate>Mon, 05 Oct 2026 00:00:00 +0000</pubDate><guid>https://www.paul-piper.de/posts/tiered-compilation-jvm-vs-julia/</guid><description>I spent fifteen years tuning JVMs for banks, retailers and insurers, and it took building a Julia plugin to notice how much of that tuning HotSpot does for you before you ever touch a flag.
The problem HotSpot solves is the one every JIT has: interpreted code starts instantly and runs slow, compiled native code starts slow and runs fast. You cannot have both from the first line. HotSpot&amp;rsquo;s answer, tiered compilation, has been the default since Java 7, and it works by never picking just one option.</description></item><item><title>Joovy - Tiered Compilation for Julia</title><link>https://www.paul-piper.de/posts/joovy-released/</link><pubDate>Wed, 12 Aug 2026 00:00:00 +0000</pubDate><guid>https://www.paul-piper.de/posts/joovy-released/</guid><description>&lt;p>&lt;a href="https://github.com/ilscipio/joovy" target="_blank" rel="noopener noreferrer">Joovy&lt;/a> is out - Apache 2.0, on GitHub.&lt;/p>
&lt;p>The name is Julia + Groovy. Groovy gave Java a dynamic layer without leaving the JVM. Joovy does the same for Julia.&lt;/p></description></item></channel></rss>