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 Matt Spitz, bquinlan, dmacnet, iunknwn, josh.r, pitrou, tomMoral, torsten
Date 2018-04-08.18:32:20
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1523212340.14.0.682650639539.issue24882@psf.upfronthosting.co.za>
In-reply-to
Content
I'm not fond of this proposal.  The existing behaviour is harmless; especially for a thread pool, since threads are cheap resources.  Improving the logic a bit might seem nice, but it also complicates the executor implementation a bit more.

Besides, once the N threads are spawned, they remain alive until the executor is shut down. So all it takes is a spike in incoming requests and you don't save resources anymore.
History
Date User Action Args
2018-04-08 18:32:20pitrousetrecipients: + pitrou, bquinlan, torsten, josh.r, Matt Spitz, tomMoral, dmacnet, iunknwn
2018-04-08 18:32:20pitrousetmessageid: <1523212340.14.0.682650639539.issue24882@psf.upfronthosting.co.za>
2018-04-08 18:32:20pitroulinkissue24882 messages
2018-04-08 18:32:20pitroucreate