5 ms·
I personally think tracing JIT is a bad technology. It's over complicated and makes it hard to reason about runtime space and time efficiencies of code. I don'
by fnord123 6y ago
I personally think tracing JIT is a bad technology. It's over complicated and makes it hard to reason about runtime space and time efficiencies of code.
I don't know the best route for python to get more performance but it probably involves allowing people to opt out of dynamism and basically doing what cython does but for all possible code.
- oefrha 6y agoYou're basically talking about mypyc: https://github.com/python/mypy/tree/master/mypyc https://github.com/python/mypy/tree/master/mypyc
- coldtea 6y ago>I personally think tracing JIT is a bad technology. It's over complicated and makes it hard to reason about runtime space and time efficiencies of code. Hasn't Strongtalk, Java, and JS put those concerns to sleep?
- rurban 6y agoAlso LuaJit. But just the most basic optimizations as done in PHP, a good lisp, scheme or lua would reach the 5x goal.
- fnord123 6y agoNo, trying to benchmark Java and JS are the reason for the concerns.
- jashmatthews 6y agoNone of the current Java or JS engines use tracing JITs, though?
- fnord123 6y agoIs there a precise difference between how openjdk works where it needs a warmup to begin running performantly and how a tracing jit works? If there a precise difference between how Ignition and Turbofan interact that is not a tracing jit? I really thought both Java and JS implementations were tracing jits. Because if I'm going to whinge about technology I don't like I want to whinge about the precise problem. :)
- coldtea 6y agoYeah, if we only had closer speed to Java and JS for CPython, I'd have no concern...