On Apr 22, 10:30 pm, Scott David Daniels
wrote:
> Michal Chruszcz wrote:
> > ... First idea, which came to my mind, was using a queue. I've got many
> > producers (all of the workers) and one consumer. Seams quite simple,
> > but it isn't, at least for me. I pre
=1)
> except Empty:
> pass
This one isn't generic. When I have tasks that all finish within 0.1
seconds the above gives 10x overhead. On the other hand, if I know the
results will be available after 10 hours there's no use in checking
every second.
Best regards
start()
>>> parent.recv()
1
>>> child.closed
False
>>> parent.recv()
... and hangs. No idea of fixing this, not even of a workaround, which
would solve my problem.
Most possibly I'm missing something in philosophy of multiprocessing,
but I couldn't find anything covering such a situation. I'd appreciate
any kind of hint on this topic, as it became a riddle I just have to
solve. :-)
Best regards,
Michal Chruszcz
--
http://mail.python.org/mailman/listinfo/python-list
