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 0x666
Recipients 0x666, amaury.forgeotdarc, jnoller, pitrou
Date 2009-01-19.19:17:10
SpamBayes Score 0.0025725986
Marked as misclassified No
Message-id <1232392631.43.0.537068028857.issue5000@psf.upfronthosting.co.za>
In-reply-to
Content
Thanks for quick response and for informative answers, especially 
thanks to Antoine Pitrou/Amaury Forgeot.

p.s.
By seting bigger range - range(15) and elements = 1000, I was able to 
get speed-up factor up to 1.8. Wow, I`m amazed :-)
Good library, keep it up.
BTW, about warp-up,- forking first processes. User can forget 
to "warpup" pool. It would be cool if pool somehow warm-ups itself in 
initialization phase (in step mul.Pool(processes=mul.cpu_count())).
Maybe you can define another initialization parameter=function ? (if 
not None, first processes should be spawned, not waiting map function) 
or something like that. But it is only cosmetics :-)
History
Date User Action Args
2009-01-19 19:17:110x666setrecipients: + 0x666, amaury.forgeotdarc, pitrou, jnoller
2009-01-19 19:17:110x666setmessageid: <1232392631.43.0.537068028857.issue5000@psf.upfronthosting.co.za>
2009-01-19 19:17:100x666linkissue5000 messages
2009-01-19 19:17:100x666create