"High water" Memory fragmentation still a thing?

Sturla Molden sturla.molden at gmail.com
Sat Oct 4 19:51:28 CEST 2014

Steven D'Aprano <steve+comp.lang.python at pearwood.info> wrote:

> [Aside: The thing that people fail to understand is that the GIL is not in
> fact something which *prevents* multi-tasking, but it *enables* cooperative
> multi-tasking:
> http://www.dabeaz.com/python/GIL.pdf
> although that's not to say that there aren't some horrible performance
> characteristics of the GIL. David Beazley has identified issues with the
> GIL which suggest room for improving the GIL and avoiding "GIL battles"
> which are responsible for much of the overhead of CPU-bound threads. Any C
> programmers who want to hack on the interpreter core?]

Didn't the "new GIL" fix some of these problems?


More information about the Python-list mailing list