rebalance(self, futures=None, workers=None, **kwargs)
Move data between workers to roughly balance memory burden. This either affects a subset of the keys/workers or the entire network, depending on keyword arguments.
For details on the algorithm and configuration options, refer to the matching scheduler-side method ~distributed.scheduler.Scheduler.rebalance
.
This operation is generally not well tested against normal operation of the scheduler. It is not recommended to use it while waiting on computations.
A list of futures to balance, defaults all data
A list of workers on which to balance, defaults to all workers
Rebalance data within network
The following pages refer to to this document either explicitly or contain code examples using this.
distributed.client.Client.replicate
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