[Python-Dev] "Fixing" the new GIL

Kristján Valur Jónsson kristjan at ccpgames.com
Wed Mar 17 12:08:39 CET 2010

> -----Original Message-----
> From: Nick Coghlan [mailto:ncoghlan at gmail.com]
> Sent: 16. mars 2010 22:08
> To: Kristján Valur Jónsson
> Cc: Antoine Pitrou; python-dev at python.org
> Subject: Re: [Python-Dev] "Fixing" the new GIL
> Kristján Valur Jónsson wrote:
> >  We have never had high priority for IO threads in
> > python (and its not-by-design round robin scheduler on single core
> > cpus) and it is unclear why that should be required now as a fix.
> David explained that in the issue tracker - 2.x typically doesn't do
> that much work per bytecode instruction, so the interpreter releases
> and
> reacquires the GIL far more frequently in a CPU-bound thread than it
> does under the new time-based check interval.
Okay, but my original post in this thread was "why don't we fix the original
problem with the GIL as implemented in 2.x" rather than to try to beat the new, more complicated, GIL into submission?
In fact, I probably should submit a patch to do that since 2.x isn't disappearing quite yet.


More information about the Python-Dev mailing list