Hacker News Reader

>If no-GIL has a 10% single thread performance hit, that means that essentially all my existing python code would be that much worse.

So? Especially since the "Faster Python" team already made Python 1.11 "10–60% Faster than 3.10", and 1.12 is even faster still, whereas their overall plan is to get it to 2-5 times faster compared to 3.9.

So at the worst case, with a 10% hit, you'd balance out the 3.11 speed, and your code would be as fast as 3.10.

View on HN

But your software would still run 10% slower than it needs to. Single threaded code is like 99% of all code written.

that's not an argument either, as your software is already 10000% slower than it needs to be as you have written it in python.

>But your software would still run 10% slower than it needs to

There's no absolute objective "needs to" or even any static baseline. Python can have, and often has had, a performance regression that drop your code by 10% at any time. It's no big deal in itself.

Also consider a further speedup of e.g. 50% in upcoming versions (they have promised more).

If you're OK with the X speed of today's Python, you should be ok with X + 40% - even if it's not the X + 50% it could have been due to the 10% GIL's removal toll.

Reply on news.ycombinator.com