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 bquinlan, gregory.p.smith, jyasskin, pitrou
Date 2011-03-22.17:36:39
SpamBayes Score 0.122494
Marked as misclassified No
Message-id <>
concurrent.futures uses polling in its worker threads and processes
(with a timeout of 0.1).
It means that:
1) this prevents CPUs to enter low power states durably
2) it incurs latency when calling shutdown() on an executor (this seems to be the main source of slowness in test_concurrent_futures under Linux)
Date User Action Args
2011-03-22 17:36:40pitrousetrecipients: + pitrou, gregory.p.smith, bquinlan, jyasskin
2011-03-22 17:36:39pitrousetmessageid: <>
2011-03-22 17:36:39pitroulinkissue11635 messages
2011-03-22 17:36:39pitroucreate