Python 3.13 Gets a JIT
tonybaloney.github.io
Python 3.13 Gets a JIT
1–10 of 553 posts
Re: Python 3.13 Gets a JIT
#2Brandt gave a talk about this at the CPython Core Developer Sprint late last year https://www.youtube.com/watch?v=HxSHIpEQRjs
Re: Python 3.13 Gets a JIT
#3For the lazy who just want to know if this makes Python faster yet, this is foundational work to enable later improvements:
> The initial benchmarks show something of a 2-9% performance improvement.
> I think that whilst the first version of this JIT isn’t going to seriously dent any benchmarks (yet), it opens the door to some huge optimizations and not just ones that benefit the toy benchmark programs in the standard benchmark suite.
Re: Python 3.13 Gets a JIT
#4> The initial benchmarks show something of a 2-9% performance improvement. You might be disappointed by this number, especially since this blog post has been talking about assembly and machine code and nothing is faster than that right?
Indeed, reading the blog post build much higher expectations
Re: Python 3.13 Gets a JIT
#5The bit everyone wants:
> The initial benchmarks show something of a 2-9% performance improvement.
Which is underwhelming (as mentioned in the article), especially if we look at PyPy[0]. But it's a step forward nonetheless.
Re: Python 3.13 Gets a JIT
#6I always wondered how Python can be one of the world's most popular languages without anyone (company) stepping up and make the runtime as fast as modern JavaScript runtimes.
Re: Python 3.13 Gets a JIT
#7I always wondered how Python can be one of the world's most popular languages without anyone (company) stepping up and make the runtime as fast as modern JavaScript runtimes.
Because enough users find the performance sufficient.
Re: Python 3.13 Gets a JIT
#8I always wondered how Python can be one of the world's most popular languages without anyone (company) stepping up and make the runtime as fast as modern JavaScript runtimes.
Because the reason why Python is one of the world's most popular language (a large set of scientific computing C extensions) is bound to every implementation details of the interpreter itself.
Re: Python 3.13 Gets a JIT
#9This was a fantastic, very clear, write-up on the subject. Thanks for sharing!
If the further optimizations that this change allows, as explained at the end of this post, are covered as well as this one, it promises to be a very interesting series of blog posts.
Re: Python 3.13 Gets a JIT
#10I always wondered how Python can be one of the world's most popular languages without anyone (company) stepping up and make the runtime as fast as modern JavaScript runtimes.
Easy and the number-crunching libs are optimized away in (generally) C.