Python 3.15’s interpreter for Windows x86-64 should hopefully be 15% faster
101–110 of 164 posts
Re: Python 3.15’s interpreter for Windows x86-64 should hopefully be 15% faster
#102This seems like very low hanging fruit. How is the core loop not already hyper optimized? I'd have expected it to be hand rolled assembly for the major ISAs, with a C backup for less common ones. How much energy has been wasted worldwide because of a relatively unoptimized interpreter?
Python’s goal is never really to be fast. If that were its goal, it would’ve had a JIT long ago instead of toying with optimizing the interpreter. Guido prioritized code simplicity over speed. A lot of speed improvements including the JIT (PEP 744 – JIT Compilation) came about after he stepped down.
So the problem is basically that a simple JIT is not beneficial for Python. So you have to invest a lot of time and effort to get a few percent faster on a typical workload. Or you have to tighten up the language and/or break the C ABI, but then you break many existing popular libraries.
Re: Python 3.15’s interpreter for Windows x86-64 should hopefully be 15% faster
#103Earlier quoted context omitted.
Games and Proton. Apparently people that care about performance do run Windows.
None of those games, or a very small amount of them, are written in python. None of the ones that need to be performant for sure.
Re: Python 3.15’s interpreter for Windows x86-64 should hopefully be 15% faster
#104I have quetion - slightly off topic, but related. I was wandering why is pyhton interpreter so much slower than V8 javascript interpreter when both javascript and python are dynamic interpreted languages.
Also Python has a de facto stable(ish) C ABI for extensions that is 1) heavily used by popular libraries, and 2) makes life more difficult for the JIT because the native code has all the same expressive power wrt Python objects, but JIT can't do code analysis to ensure that it doesn't use it.
Re: Python 3.15’s interpreter for Windows x86-64 should hopefully be 15% faster
#105I don't understand this focus on micro performance details... considering that all of this is about an interpretation approach which is always going to be slow relatively speaking. The big speed up would be to JIT it all, then you dont need to care about structuring of switch loops etc
Re: Python 3.15’s interpreter for Windows x86-64 should hopefully be 15% faster
#106Re: Python 3.15’s interpreter for Windows x86-64 should hopefully be 15% faster
#107Re: Python 3.15’s interpreter for Windows x86-64 should hopefully be 15% faster
#108Re: Python 3.15’s interpreter for Windows x86-64 should hopefully be 15% faster
#109After years of admonition discouraging me, I’m using Python for a Windows GUI app over my usual C#/MAUI. I’m much more familiar with Python and the whole VS ecosystem is just so heavy for lightweight tasks. I started with tkinter but found it super clunky for interactions I needed heavily, like on field change, but learning QT seemed like more of a lift than I was interested in. (Maybe a skill issue on both fronts?)…
Re: Python 3.15’s interpreter for Windows x86-64 should hopefully be 15% faster
#110After years of admonition discouraging me, I’m using Python for a Windows GUI app over my usual C#/MAUI. I’m much more familiar with Python and the whole VS ecosystem is just so heavy for lightweight tasks. I started with tkinter but found it super clunky for interactions I needed heavily, like on field change, but learning QT seemed like more of a lift than I was interested in. (Maybe a skill issue on both fronts?)…