Live data from Hacker News

Python 3.15’s interpreter for Windows x86-64 should hopefully be 15% faster

fidget-spinner.github.io

71–80 of 164 posts

Re: Python 3.15’s interpreter for Windows x86-64 should hopefully be 15% faster

#71
post #46
post #35

Earlier quoted context omitted.

Probably because anyone concerned with performance wasn’t running workloads on Windows to begin with.

Games and Proton. Apparently people that care about performance do run Windows.

But not python.

Re: Python 3.15’s interpreter for Windows x86-64 should hopefully be 15% faster

#72
post #27

Im a bit out of the loop with this, but hope its not like that time with python 3.14, when it was claimed a geometric mean speedup of about 9-15% over the standard interpreter when built with Clang 19. It turned out the results were inflated due to a bug in LLVM 19 that prevented proper "tail duplication" optimization in the baseline interpreter's dispatch loop. Actual gains was aprox 4%. Edit: Read through it and ha…

I’ll repeat what I said at that time: one of the benefits of the new design is that it’s less vulnerable to the whims of the optimizer: https://news.ycombinator.com/item?id=43322451 If getting the optimal code is relying on getting a pile of heuristics to go in your favor, you’re more vulnerable to the possibility that someday the heuristics will go the other way. Tail duplication is what we want in case, but it’s po…

Yeah, I believe that statement and it seems to hold true for MSVC as well. Thanks for your work inspiring all of this btw!

Re: Python 3.15’s interpreter for Windows x86-64 should hopefully be 15% faster

#74
post #53
post #46

Earlier 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.

Indeed, but the question was about performance in general.

Re: Python 3.15’s interpreter for Windows x86-64 should hopefully be 15% faster

#75
post #52
post #46

Earlier quoted context omitted.

Games and Proton. Apparently people that care about performance do run Windows.

Games are made for windows because that's where the device drivers have historically been. Any other viewpoint is ignoring reality.

Sure, keep believing that while loading Proton.

Re: Python 3.15’s interpreter for Windows x86-64 should hopefully be 15% faster

#77
post #50

I 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.

I can think of two possible reasons: First is the Google's manpower. Google somehow succeeds in writing fast software. Most Google products I use are fast in contrast to the rest of the ecosystem. It's possible that Google simply did a better job. The second is CPython legacy. There are faster implementations of Python that completely implement the API (PyPy comes to mind), but there's a huge ecosystem of C extension…

Don't forget that there was a Google attempt at making a faster Python - Unladen Swallow. It got lots of PR but never merged with mainline CPython (wikipedia says a dev branch was released).

see https://en.wikipedia.org/wiki/Unladen_Swallow

Re: Python 3.15’s interpreter for Windows x86-64 should hopefully be 15% faster

#78
post #45

Earlier quoted context omitted.

Important enough, or benefits them directly? I have no good guesses how improving Python's performance would benefit them, but I would guess that's the real reason.

Microsoft was the one hiring Guido out of retirement, and alongside Facebook finally kicking off the CPython JIT efforts. Python is one of the Microsoft blessed languages on their devblogs.

The project was first suggested by Mark Shannon. Van Rossum inserted himself into the project. Faster CPython people have been fired by Microsoft last year.

Generally not that much has happened in 5 years, sometimes 10-15% improvements are posted that are later offset by bloat.

I think the project started in 3.10, so 3.9 is the last version to compare to. The improvements aren't that great, I don't think any other language would get so much positive feedback for so little.

Post reply on HN