Back to Ray

Pattern: Using asyncio to run actor methods concurrently

doc/source/ray-core/patterns/concurrent-operations-async-actor.rst

1.13.11.7 KB
Original Source

Pattern: Using asyncio to run actor methods concurrently

By default, a Ray :ref:actor <ray-remote-classes> runs in a single thread and actor method calls are executed sequentially. This means that a long running method call blocks all the following ones. In this pattern, we use await to yield control from the long running method call so other method calls can run concurrently. Normally the control is yielded when the method is doing IO operations but you can also use await asyncio.sleep(0) to yield control explicitly.

.. note:: You can also use :ref:threaded actors <threaded-actors> to achieve concurrency.

Example use case

You have an actor with a long polling method that continuously fetches tasks from the remote store and executes them. You also want to query the number of tasks executed while the long polling method is running.

With the default actor, the code will look like this:

.. literalinclude:: ../doc_code/pattern_async_actor.py :language: python :start-after: sync_actor_start :end-before: sync_actor_end

This is problematic because TaskExecutor.run method runs forever and never yields control to run other methods. We can solve this problem by using :ref:async actors <async-actors> and use await to yield control:

.. literalinclude:: ../doc_code/pattern_async_actor.py :language: python :start-after: async_actor_start :end-before: async_actor_end

Here, instead of using the blocking :func:ray.get() <ray.get> to get the value of an ObjectRef, we use await so it can yield control while we are waiting for the object to be fetched.