This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author dabeaz
Recipients beazley, dabeaz, flox, kristjan.jonsson, loewis, pitrou, torsten
Date 2010-04-07.00:08:18
SpamBayes Score 1.941145e-05
Marked as misclassified No
Message-id <1270598901.29.0.167972116991.issue8299@psf.upfronthosting.co.za>
In-reply-to
Content
The analysis of instruction cache behavior is interesting---I could definitely see that coming into play given the heavy penalty that one sees going to multiple cores (it's a side effect in addition everything else that goes wrong such as a huge increase in the number of system calls).

I will only point out that messing around with processor affinities is going to be problematic.  There are C/C++ extensions to Python that intentionally release the GIL and want to run fully multithreaded across as many cores as might be available.  Setting a processor affinities is going to be the exact opposite of what you want for code like that.
History
Date User Action Args
2010-04-07 00:08:21dabeazsetrecipients: + dabeaz, loewis, beazley, pitrou, kristjan.jonsson, flox, torsten
2010-04-07 00:08:21dabeazsetmessageid: <1270598901.29.0.167972116991.issue8299@psf.upfronthosting.co.za>
2010-04-07 00:08:19dabeazlinkissue8299 messages
2010-04-07 00:08:18dabeazcreate