➜
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.
Created on 2013-10-05 17:30 by noxdafox, last changed 2022-04-11 14:57 by admin.
| Files | ||||
|---|---|---|---|---|
| File name | Uploaded | Description | Edit | |
| maxqueuesize.patch | noxdafox, 2013-10-05 17:30 | review | ||
| maxqueuesize.patch | noxdafox, 2013-10-05 17:34 | review | ||
| Messages (3) | |||
|---|---|---|---|
| msg198992 - (view) | Author: Matteo Cafasso (noxdafox) | Date: 2013-10-05 17:30 | |
As a developer I want the multiprocessing Pool class to expose the internal queue size limit in order to better control the task flow in my application. Consider the following scenarios: 1. The tasks I want to run into the pool require a considerably big amount of data as input (a big XML string for example). A limitless queue and a high number of tasks would cause my application to consume a huge amount of memory, this is unacceptable. 2. I want to always ensure a small amount of tasks queued into the pool so that, if my application crashes, I won't loose much data. Patch includes code changes, tests and documentation. |
|||
| msg198993 - (view) | Author: Matteo Cafasso (noxdafox) | Date: 2013-10-05 17:34 | |
Please ignore the first provided patch, doc changes where wrong |
|||
| msg315246 - (view) | Author: Antoine Pitrou (pitrou) *  |
Date: 2018-04-13 14:15 | |
A similar issue for concurrent.futures is bpo-29595. |
|||
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2022-04-11 14:57:51 | admin | set | github: 63372 |
| 2018-04-13 14:15:39 | pitrou | set | messages:
+ msg315246 versions: + Python 3.8, - Python 3.4 |
| 2018-04-12 19:35:34 | ned.deily | set | nosy:
+ pitrou, davin |
| 2013-10-05 20:54:31 | pitrou | set | nosy:
+ sbt |
| 2013-10-05 17:34:55 | noxdafox | set | files:
+ maxqueuesize.patch messages: + msg198993 |
| 2013-10-05 17:30:41 | noxdafox | create | |