Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.python > #74595 > unrolled thread

Re: Anything better than asyncio.as_completed() and asyncio.wait() to manage execution of large amount of tasks?

Started byMaxime Steisel <maximesteisel@gmail.com>
First post2014-07-17 01:09 +0200
Last post2014-07-22 09:20 -0700
Articles 2 — 2 participants

Back to article view | Back to comp.lang.python

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: Anything better than asyncio.as_completed() and asyncio.wait() to manage execution of large amount of tasks? Maxime Steisel <maximesteisel@gmail.com> - 2014-07-17 01:09 +0200
    Re: Anything better than asyncio.as_completed() and asyncio.wait() to manage execution of large amount of tasks? CHIN Dihedral <dihedral88888@gmail.com> - 2014-07-22 09:20 -0700

#74595 — Re: Anything better than asyncio.as_completed() and asyncio.wait() to manage execution of large amount of tasks?

FromMaxime Steisel <maximesteisel@gmail.com>
Date2014-07-17 01:09 +0200
SubjectRe: Anything better than asyncio.as_completed() and asyncio.wait() to manage execution of large amount of tasks?
Message-ID<mailman.11904.1405552164.18130.python-list@python.org>
2014-07-15 14:20 GMT+02:00 Valery Khamenya <khamenya@gmail.com>:
> Hi,
>
> both asyncio.as_completed() and asyncio.wait() work with lists only. No
> generators are accepted. Are there anything similar to those functions that
> pulls Tasks/Futures/coroutines one-by-one and processes them in a limited
> task pool?


Something like this (adapted from as_completed) should do the work:

import asyncio
from concurrent import futures

def parallelize(tasks, *, loop=None, max_workers=5, timeout=None):
    loop = loop if loop is not None else asyncio.get_event_loop()
    workers = []
    pending = set()
    done = asyncio.Queue(maxsize=max_workers)
    exhausted = False

    @asyncio.coroutine
    def _worker():
        nonlocal exhausted
        while not exhausted:
            try:
                t = next(tasks)
                pending.add(t)
                yield from t
                yield from done.put(t)
                pending.remove(t)
            except StopIteration:
                exhausted = True

    def _on_timeout():
        for f in workers:
            f.cancel()
        workers.clear()
        #Wake up _wait_for_one()
        done.put_nowait(None)

    @asyncio.coroutine
    def _wait_for_one():
        f = yield from done.get()
        if f is None:
            raise futures.TimeoutError()
        return f.result()

    workers = [asyncio.async(_worker()) for i in range(max_workers)]

    if workers and timeout is not None:
        timeout_handle = loop.call_later(timeout, _on_timeout)

    while not exhausted or pending or not done.empty():
        yield _wait_for_one()

    timeout_handle.cancel()

[toc] | [next] | [standalone]


#75004

FromCHIN Dihedral <dihedral88888@gmail.com>
Date2014-07-22 09:20 -0700
Message-ID<e76f3128-1ae0-4046-83bc-feb81932fad4@googlegroups.com>
In reply to#74595
On Thursday, July 17, 2014 7:09:02 AM UTC+8, Maxime Steisel wrote:
> 2014-07-15 14:20 GMT+02:00 Valery Khamenya <khamenya@gmail.com>:
> 
> > Hi,
> 
> >
> 
> > both asyncio.as_completed() and asyncio.wait() work with lists only. No
> 
> > generators are accepted. Are there anything similar to those functions that
> 
> > pulls Tasks/Futures/coroutines one-by-one and processes them in a limited
> 
> > task pool?
> 
> 
> 
> 
> 
> Something like this (adapted from as_completed) should do the work:
> 
> 
> 
> import asyncio
> 
> from concurrent import futures
> 
> 
> 
> def parallelize(tasks, *, loop=None, max_workers=5, timeout=None):
> 
>     loop = loop if loop is not None else asyncio.get_event_loop()
> 
>     workers = []
> 
>     pending = set()
> 
>     done = asyncio.Queue(maxsize=max_workers)
> 
>     exhausted = False
> 
> 
> 
>     @asyncio.coroutine
> 
>     def _worker():
> 
>         nonlocal exhausted
> 
>         while not exhausted:
> 
>             try:
> 
>                 t = next(tasks)
> 
>                 pending.add(t)
> 
>                 yield from t
> 
>                 yield from done.put(t)
> 
>                 pending.remove(t)
> 
>             except StopIteration:
> 
>                 exhausted = True
> 
> 
> 
>     def _on_timeout():
> 
>         for f in workers:
> 
>             f.cancel()
> 
>         workers.clear()
> 
>         #Wake up _wait_for_one()
> 
>         done.put_nowait(None)
> 
> 
> 
>     @asyncio.coroutine
> 
>     def _wait_for_one():
> 
>         f = yield from done.get()
> 
>         if f is None:
> 
>             raise futures.TimeoutError()
> 
>         return f.result()
> 
> 
> 
>     workers = [asyncio.async(_worker()) for i in range(max_workers)]
> 
> 
> 
>     if workers and timeout is not None:
> 
>         timeout_handle = loop.call_later(timeout, _on_timeout)
> 
> 
> 
>     while not exhausted or pending or not done.empty():
> 
>         yield _wait_for_one()
> 
> 
> 
>     timeout_handle.cancel()

Well, I think you are missing the 
task managers as workers in your flow
of logics. 

I suggest a better version is 
with a global signal of 8 to 16 times clock of the normal worker pace in 
order to cope with ASYN events 
accordingly for the workers which colud be  decorated to yield, but not in the worker's funtions.

[toc] | [prev] | [standalone]


Back to top | Article view | comp.lang.python


csiph-web