fix path

Author: Fidget-Spinner

_posts/2026-03-17-jit-on-track.md

@@ -5,10 +5,10 @@ title: Python 3.15's JIT is now back on track
 
 17 Mar 2026
 
-![JIT performance as of 17 March (PST). Lower is better versus interpreter]({{ site.baseurl }}/media/brrr-20260318.png)
+![JIT performance as of 17 March (PST). Lower is better versus interpreter]({{ site.baseurl }}/media/jit-on-track/brrr-20260318.png)
 (JIT performance as of 17 March (PST). Lower is better versus interpreter. Image credits to https://doesjitgobrrr.com/).
 
-Great news---we've hit our performance goals for the CPython JIT over a year early for macOS AArch64, and a few months early for x86_64 Linux. The 3.15 alpha JIT is about **11-12%** faster on macOS AArch64 than the tail calling interpreter, and **5-6%** faster than the standard interpreter on x86_64 Linux. These [numbers](https://doesjitgobrrr.com/run/2026-03-17) are geometric means and are preliminary. The actual range is something like a **20% slowdown to over 100% speedup** (ignoring the ``unpack_sequence`` microbenchmark). We don't have proper free-threading support yet, but we're aiming for that in 3.15/3.16. The JIT is now back on track.
+Great news---we've hit our (very modest) performance goals for the CPython JIT over a year early for macOS AArch64, and a few months early for x86_64 Linux. The 3.15 alpha JIT is about **11-12%** faster on macOS AArch64 than the tail calling interpreter, and **5-6%** faster than the standard interpreter on x86_64 Linux. These [numbers](https://doesjitgobrrr.com/run/2026-03-17) are geometric means and are preliminary. The actual range is something like a **20% slowdown to over 100% speedup** (ignoring the ``unpack_sequence`` microbenchmark). We don't have proper free-threading support yet, but we're aiming for that in 3.15/3.16. The JIT is now back on track.
 
 **I cannot understate how tough this was**. There was a point where I was seriously wondering if the JIT project would ever produce meaningful speedups. To recap, the original CPython JIT had practically no speedups: 8 months ago I posted a [JIT reflections article]({{ site.baseurl }}/posts/jit-reflections.html) on how the original CPython JIT in 3.13 and 3.14 was often slower than the interpreter. That was also around the time where the Faster CPython team lost funding by its main sponsor. I'm a volunteer so this didn't affect me, but more importantly it did affect my friends working there, and at a point of time it seemed the JIT's future was uncertain.