Keys often have a structure like ("x-123", 0)
A group takes the first section, like "x-123"
.. attribute:: name: str
The name of a group of tasks.
For a task like ``("x-123", 0)`` this is the text ``"x-123"``
.. attribute:: states: Dict[str, int]
The number of tasks in each state,
like ``{"memory": 10, "processing": 3, "released": 4, ...}``
.. attribute:: dependencies: Set[TaskGroup]
The other TaskGroups on which this one depends
.. attribute:: nbytes_total: int
The total number of bytes that this task group has produced
.. attribute:: duration: float
The total amount of time spent on all tasks in this TaskGroup
.. attribute:: types: Set[str]
The result types of this TaskGroup
.. attribute:: last_worker: WorkerState
The worker most recently assigned a task from this group, or None when the group
is not identified to be root-like by `SchedulerState.decide_worker`.
.. attribute:: last_worker_tasks_left: int
If `last_worker` is not None, the number of times that worker should be assigned
subsequent tasks until a new worker is chosen.
Collection tracking all tasks within a group
The following pages refer to to this document either explicitly or contain code examples using this.
distributed.scheduler.Computation
distributed.scheduler.TaskPrefix
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