progress(*futures, notebook=None, multi=True, complete=True, **kwargs)
This operates differently in the notebook and the console
Notebook: This returns immediately, leaving an IPython widget on screen
Console: This blocks until the computation completes
In the notebook, the output of progress
must be the last statement in the cell. Typically, this means calling progress
at the end of a cell.
A list of futures or keys to track
Running in the notebook or not (defaults to guess)
Track different functions independently (defaults to True)
Track all keys (True) or only keys that have not yet run (False) (defaults to True)
Track progress of futures
>>> progress(futures) # doctest: +SKIP [########################################] | 100% Completed | 1.7sSee :
The following pages refer to to this document either explicitly or contain code examples using this.
distributed.diagnostics.progressbar.progress
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