News for hackers. Stuff that matters.
Re:Python stands to lose its GIL, and gain a lot of speed by jhoechtl on Sunday October 17, 2021 @02:33PM (#28898622)
OS overhead of 128 processes is higher than scheduling 128 tasks. Varies from os to os, but it's especially bad on Windows.
Re:Python stands to lose its GIL, and gain a lot of speed by turminal on Sunday October 17, 2021 @02:40PM (#28898677)
Yeah, I know about that argument but it just doesn't make sense to me. Removing the GIL means that 1) you make your language runtime more complex and 2) you make your app more complex.

Is it truly worth it just to avoid some memory overhead? Or is there some other windows specific thing that I'm missing here?

Re:Python stands to lose its GIL, and gain a lot of speed by dragonwriter on Sunday October 17, 2021 @02:44PM (#28898716)
> Yeah, I know about that argument but it just doesn't make sense to me. Removing the GIL means that 1) you make your language runtime more complex and 2) you make your app more complex.

#2 need not be true; e.g., the approach proposed here is transparent to most Python code and even minimized impact on C extensions, still exposing the same GIL hook functions which C code would use in the same circumstances, though it has slightly different effect.

Re:Python stands to lose its GIL, and gain a lot of speed by lmm on Sunday October 17, 2021 @09:16PM (#28901318)
It doesn't have to be. On Linux 2.4 (pre-NPTL) processes and threads were represented exactly the same way.