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 cool-RR
Recipients cool-RR, pitrou
Date 2021-07-24.12:14:41
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1627128881.56.0.324294431588.issue44733@roundup.psfhosted.org>
In-reply-to
Content
I love `concurrent.futures`, and I'd like to use it wherever I can. There's a feature in `multiprocessing.Pool` that I wish would also be available in `ProcessPoolExecutor`: The `maxtasksperchild` argument.

Documentation: "maxtasksperchild is the number of tasks a worker process can complete before it will exit and be replaced with a fresh worker process, to enable unused resources to be freed. The default maxtasksperchild is None, which means worker processes will live as long as the pool."

I want to be able to set it to 1, so each process will only execute one task and then be replaced with a fresh process.
History
Date User Action Args
2021-07-24 12:14:41cool-RRsetrecipients: + cool-RR, pitrou
2021-07-24 12:14:41cool-RRsetmessageid: <1627128881.56.0.324294431588.issue44733@roundup.psfhosted.org>
2021-07-24 12:14:41cool-RRlinkissue44733 messages
2021-07-24 12:14:41cool-RRcreate