[Python-Dev] "Fixing" the new GIL

Bill Janssen janssen at parc.com
Tue Mar 16 16:11:39 CET 2010

Martin v. Löwis <martin at v.loewis.de> wrote:

> > If it's lurking behind a filesystem interface or in its daemon mode
> > (remote archive store), multiple client processes can be using it at once,
> > and it will be processing multiple tasks somewhat in parallel. Here one
> > can get a compute bound thread answering one request, impacting quick
> > response to other parallel-and-cheap requests.
> However, "impacting" will always be the case. *Of course* any thread
> that performs computation impacts everything else on the same processor.

That's not the problem, Martin.  The problem is that it also impacts
other threads on other cores, because of the interlock between the OS
thread scheduler and the internal Pythonic struggle to obtain the GIL.
And it shouldn't.


More information about the Python-Dev mailing list