Message102507
| 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. |
|