From c7f0b303f34ff166744eebdabab8b6815536fc74 Mon Sep 17 00:00:00 2001 From: Richard Liaw Date: Wed, 4 Mar 2020 13:35:46 -0800 Subject: [PATCH] Mention that calling some_function.remote() is non-blocking (#7417) * Mention that calling some_function.remote() is non-blocking. * Apply suggestions from code review Co-authored-by: Richard Liaw --- doc/source/walkthrough.rst | 3 +++ 1 file changed, 3 insertions(+) diff --git a/doc/source/walkthrough.rst b/doc/source/walkthrough.rst index 0279dc821..9959f9c20 100644 --- a/doc/source/walkthrough.rst +++ b/doc/source/walkthrough.rst @@ -82,6 +82,9 @@ This causes a few changes in behavior: for _ in range(4): remote_function.remote() +The invocations are executed in parallel because the call to ``remote_function.remote()`` doesn't block. +All computation is performed in the background, driven by Ray's internal event loop. + See the `ray.remote package reference `__ page for specific documentation on how to use ``ray.remote``. **Object IDs** can also be passed into remote functions. When the function actually gets executed, **the argument will be a retrieved as a regular Python object**. For example, take this function: