Message256168
Thanks David. using spawn - multiprocessing.get_context('spawn').Pool(... - does the job . It does has it's flows - fork allows me to share data between workers (especially large readonly memory database, which I don't want to duplicate for each worker), which spawn (which uses fork-exec python script) doesn't. So I'll have to see about that.
I still don't understand why forking has to be done under the worker thread context. It doesn't seem like a good design - When forking from a thread you can never be sure what is being forked. A better approach seems to be to fork missing workers on-demand, synchronous to the main thread. But I probably lack the historic context of the multiprocess module. |
|
Date |
User |
Action |
Args |
2015-12-10 08:14:42 | amikoren@yahoo.com | set | recipients:
+ amikoren@yahoo.com, gps, r.david.murray, sbt |
2015-12-10 08:14:42 | amikoren@yahoo.com | set | messageid: <1449735282.15.0.638801908618.issue25829@psf.upfronthosting.co.za> |
2015-12-10 08:14:42 | amikoren@yahoo.com | link | issue25829 messages |
2015-12-10 08:14:41 | amikoren@yahoo.com | create | |
|