Despite 30 months work, core developer says Python's JIT compiler is often slower than the interpreter
Despite 30 months work, core developer says Python's JIT compiler is often slower than the interpreter • DEVCLASS
You're viewing a single thread.
Python typing system is the reason of its huge flexibility, but as many other scripting language, it’s also what makes it so hard to optimize.
I have no idea how you can change that without bringing some “JIT-oriented” features inside the Python language itself.
I still hope for the best, but I’m unsure we will be able to see an efficient JIT system inside CPython soon.
PyPy had to rewrite the whole Python implementation in a JIT focused way, and even with that, they are (not uncommon) cases when PyPy is slower.
I'm a fan of type infrence languages
i'm a fan of ladies with complete test coverage
but i'm ok with those who are a fan of type inference.
More ladies for me
I gather that you don't actually use PyPy much. On average, I expect PyPy to deliver over a 3x speedup. The main issue is that people have built upon slow libraries like Numpy that only seem fast because CPython is even slower.
The reason that CPython cannot have a JIT added on is architectural and political. The CPython core team refuses to learn lessons from PyPy.