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 pitrou
Recipients beazley, dabeaz, flox, kristjan.jonsson, loewis, pitrou, techtonik, torsten
Date 2010-04-11.12:38:52
SpamBayes Score 7.003351e-05
Marked as misclassified No
Message-id <1270989655.3494.2.camel@localhost>
In-reply-to <1270984146.83.0.532372545466.issue8299@psf.upfronthosting.co.za>
Content
> SHA1 hashing (C)
> 
> threads= 1:  1275 iterations/s. balance
> threads= 2:  1267 ( 99%)        0.7238
> threads= 3:  1271 ( 99%)        0.2405
> threads= 4:  1270 ( 99%)        0.1508
> 
> Using the forced "do_yield" helps balance things, but not much.  We
> still have a .7 balance in SHA1 hashing for two threads.

Which is not unreasonable, since SHA1 releases the GIL. The unbalance
would be produced by the Windows scheduler, not by Python.

Note: "do_yield" is not meant to "balance" things as much as to make
measurements meaningful at all. Without switching at all during say 2
seconds, the numbers become totally worthless.

> If no one objects, I'd like to submit this changed ccbench.py to the trunk.

Please let me take a look.
History
Date User Action Args
2010-04-11 12:38:54pitrousetrecipients: + pitrou, loewis, beazley, kristjan.jonsson, techtonik, flox, dabeaz, torsten
2010-04-11 12:38:52pitroulinkissue8299 messages
2010-04-11 12:38:52pitroucreate