Author nirai
Recipients DazWorrall, alex, brian.curtin, carljm, coderanger, dabeaz, eric.smith, flox, jhylton, karld, kevinwatters, loewis, mahmoudimus, nirai, pitrou, rcohen, rh0dium, tarek
Date 2010-03-16.21:17:30
SpamBayes Score 0.00258877
Marked as misclassified No
Message-id <1268774253.82.0.248764035922.issue7946@psf.upfronthosting.co.za>
In-reply-to
Content
I tried Florent's modification to the write test and did not see the effect on my machine with an updated revision of Python32.

I am running Ubuntu Karmic 64 bit.
7s - no background threads.
20s - one background thread.

According to the following documentation the libc condition is using scheduling policy when waking a thread and not FIFO order:
The following documentation suggests ordering in Linux is not FIFO:
http://www.opengroup.org/onlinepubs/000095399/functions/pthread_cond_timedwait.html#tag_03_518_08_06

I upload a quick and dirty patch (linux-7946.patch) to the new GIL just to reflect this by avoiding the timed waits.  

On my machine it behaves reasonably both with the TCP server and with the write test, but so does unpatched Python 3.2.

I noticed high context switching rate with dave's priority GIL - with both tests it goes above 40K/s context switches.
History
Date User Action Args
2010-03-16 21:17:34niraisetrecipients: + nirai, loewis, jhylton, pitrou, eric.smith, kevinwatters, tarek, karld, carljm, coderanger, alex, brian.curtin, flox, DazWorrall, rh0dium, rcohen, dabeaz, mahmoudimus
2010-03-16 21:17:33niraisetmessageid: <1268774253.82.0.248764035922.issue7946@psf.upfronthosting.co.za>
2010-03-16 21:17:32nirailinkissue7946 messages
2010-03-16 21:17:31niraicreate