News for hackers. Stuff that matters.
Re:Scaling NumPy on Free-Threaded Python by ngoldbaum on Thursday August 06, 2026 @07:14AM (#49195178)
There’s also the fact that INCREF and DECREF on shared objects is a lot more expensive than plain integer addition, so stuff becomes a bottleneck that was never a bottleneck. Kumar also fixed a bottleneck caused by a lock added only for safety on the free-threaded build. It’s hard to tell in advance than a fancy lock-free data structure is needed for something.
Re:Scaling NumPy on Free-Threaded Python by quietbritishjim on Friday August 07, 2026 @08:09AM (#49209179)
You're talking about the same thing as the article: why were things not as fast as they could be in free threaded mode?

But this comment thread is more of a meta discussion: if numpy already released the GIL, why would lock contention issues only show up now in free threaded mode? That's what I answered above (i.e. yes the GIL was sometimes released by numpy, but there operations really were happening with the GIL locked in non free threaded build).

Re:Scaling NumPy on Free-Threaded Python by ngoldbaum on Friday August 07, 2026 @09:07AM (#49209835)
I’m saying that it’s a new issue on the free-threaded build.
Re:Scaling NumPy on Free-Threaded Python by quietbritishjim on Friday August 07, 2026 @09:16AM (#49209933)
Right. The original commenter already seemed to understand that.

It's a new issue because the reference count needs locking, whereas previously it didn't because it was implicitly synchronised due to the GIL being locked.

But the original commenter asked: hang on, I thought the GIL wasn't locked for numpy?

Now you have reached the start of the conversation.