Python

Python 3.15 JIT Benchmarks Show Real Progress for Targeted Workloads

The same three Python workloads keep showing up in the JIT benchmarks, and for Python 3.15, they finally show real progress. The just-in-time compiler is delivering stronger results for targeted programs, but it still…

3 min readTowards Data Science

Python 3.15's JIT compiler is making real, measurable progress on targeted workloads, and that matters more than a blanket speedup across every possible script. The benchmarks show the same three workloads that benefited in 3.14 now run even faster, confirming the team is iterating with purpose rather than chasing flashy gains. This is the kind of honest engineering that earns trust: acknowledge the limits, then push the specific use cases that matter most.

For anyone who spends their day wrangling data in spreadsheets or notebooks, this is directly relevant. The workloads showing improvement, tight loops, numerical operations, and repeated function calls, are the same patterns that bog down manual calculations, pivot tables, and custom formulas. A faster Python runtime means those operations become snappier without you changing a single line of code. It also means the tools built on top of Python, including the AI-native spreadsheet platforms we talk about, inherit that performance for free. That's a practical win, not a marketing claim.

The honesty about what the JIT still doesn't help is equally valuable. Not every program accelerates, and pretending otherwise would undermine the credibility of the benchmarks. This mirrors a theme we've explored in Securing AI in the Cloud Means Securing Kubernetes First: real progress comes from focusing on the right foundations, not from promising everything to everyone. Similarly, when Seven Decision Models Put to the Test Against a Generative LLM compared routing accuracy and latency, the takeaway wasn't that one model dominates all tasks, it was that targeted evaluation reveals where each approach truly shines. Python's JIT team is doing the same kind of honest work.

The specific detail to watch is whether the Python core team continues to narrow the gap between JIT-accelerated and non-accelerated code in future releases. If the three targeted workloads keep improving while the rest stay flat, the practical question becomes: how many of your daily workflows actually fall into those three buckets? For data professionals and spreadsheet power users, the answer is likely more than you think. That's the real story here, not a revolution, but a steady, verifiable improvement in the places that will save you the most time.

From Towards Data Science

The same three workloads show a much stronger JIT, but it still doesn't help every program

The post I Reran My Python 3.14 JIT Benchmarks on Python 3.15 appeared first on Towards Data Science.

Read the original at Towards Data Science