Author dabeaz
Recipients beazley, dabeaz, flox, kristjan.jonsson, loewis, pitrou, r.david.murray, techtonik, torsten
Date 2010-04-17.11:16:51
SpamBayes Score 1.36649e-09
Marked as misclassified No
Message-id <>
I'm definitely sure that semaphores were being used in my test---I stuck a print statement inside the code that creates locks just to make sure it was using the semaphore version :-).

Unfortunately, at this point I think most of this discussion is academic since no change is likely to be incorporated into Python 2.7.  I can definitely see where fairness might help I/O performance if there is only 1 CPU bound thread.  I just don't know for other situations.  For example, if you have a server where it's all I/O-bound threads, but it suddenly comes under extreme load (e.g., slashdot effect), does a fair GIL help or hurt with that?  I just don't know.

In the big picture, all of the issues raised here should be on the minds of people fixing the GIL in py3k though.   It's just one more aspect of why fixing the GIL is hard.
Date User Action Args
2010-04-17 11:16:54dabeazsetrecipients: + dabeaz, loewis, beazley, pitrou, kristjan.jonsson, techtonik, r.david.murray, flox, torsten
2010-04-17 11:16:54dabeazsetmessageid: <>
2010-04-17 11:16:53dabeazlinkissue8299 messages
2010-04-17 11:16:52dabeazcreate