Re: multiprocessing, pool, queue length

From	Michael Welle <mwe012008@gmx.net>
Newsgroups	comp.lang.python
Subject	Re: multiprocessing, pool, queue length
Date	2016-03-22 07:19 +0100
Organization	MB-NET.NET for Open-News-Network e.V.
Message-ID	<mo47scx1sv.ln2@news.c0t0d0s0.de> (permalink)
References	<0qu4scx89u.ln2@news.c0t0d0s0.de> <mailman.456.1458587577.12893.python-list@python.org> <olv5scxgnt.ln2@news.c0t0d0s0.de> <mailman.465.1458595524.12893.python-list@python.org>

Show all headers | View raw

Hello,

Ian Kelly <ian.g.kelly@gmail.com> writes:

> On Mon, Mar 21, 2016 at 1:46 PM, Michael Welle <mwe012008@gmx.net> wrote:
>> Wait on the result means to set a multiprocessing.Event if one of the
>> consumers finds the sentinel task and wait for it on the producer? Hmm,
>> that might be better than incrementing a counter. But still, it couples
>> the consumers and the producer more than I like.
>
> No, I mean calling AsyncResult.wait() on the result of the sentinel
> task (or just calling Pool.apply instead of Pool.apply_async in the
> first place).
ah, I see.

Thanks
hmw

Back to comp.lang.python | Previous | Next — Previous in thread | Find similar | Unroll thread

Thread

multiprocessing, pool, queue length Michael Welle <mwe012008@gmx.net> - 2016-03-21 11:25 +0100
  Re: multiprocessing, pool, queue length Ian Kelly <ian.g.kelly@gmail.com> - 2016-03-21 13:12 -0600
    Re: multiprocessing, pool, queue length Michael Welle <mwe012008@gmx.net> - 2016-03-21 20:46 +0100
      Re: multiprocessing, pool, queue length Ian Kelly <ian.g.kelly@gmail.com> - 2016-03-21 15:24 -0600
        Re: multiprocessing, pool, queue length Michael Welle <mwe012008@gmx.net> - 2016-03-22 07:19 +0100

csiph-web