An actor allows remote control of a stateful object living on a remote worker. Method calls on this object trigger operations on the remote object and return ActorFutures on which we can block to get results.
Controls an object on a remote worker
>>> class Counter:This example is valid syntax, but we were not able to check execution
... def __init__(self):
... self.n = 0
... def increment(self):
... self.n += 1
... return self.n
>>> from dask.distributed import Client
... client = Client()
You can create an actor by submitting a class with the keyword actor=True
.
>>> future = client.submit(Counter, actor=True)
... counter = future.result()
... counter <Actor: Counter, key=Counter-1234abcd>
Calling methods on this object immediately returns deferred ActorFuture
objects. You can call .result()
on these objects to block and get the result of the function call.
>>> future = counter.increment()This example is valid syntax, but we were not able to check execution
... future.result() 1
>>> future = counter.increment()See :
... future.result() 2
The following pages refer to to this document either explicitly or contain code examples using this.
distributed.actor.ActorFuture
Hover to see nodes names; edges to Self not shown, Caped at 50 nodes.
Using a canvas is more power efficient and can get hundred of nodes ; but does not allow hyperlinks; , arrows or text (beyond on hover)
SVG is more flexible but power hungry; and does not scale well to 50 + nodes.
All aboves nodes referred to, (or are referred from) current nodes; Edges from Self to other have been omitted (or all nodes would be connected to the central node "self" which is not useful). Nodes are colored by the library they belong to, and scaled with the number of references pointing them