liveBook · Manning

Scheduler

As explained in Designing Deep Learning Systems: A guide for software engineers

A workflow-system component that detects submitted workflows and dispatches their tasks according to dependency and ordering constraints.

A scheduler is the workflow-orchestration component that watches active workflows, determines when they should run, and dispatches their tasks according to the workflow DAG’s dependency order. It commonly operates alongside a controller, while workers provide the compute resources that execute the tasks. section 9.2.1 section 9.2.2

A production scheduler fits into the orchestration system by:

  • Watching submitted and active workflows and scheduling them when their configured time arrives. section 9.2.2
  • Dispatching workflow tasks to backend workers rather than performing the task’s heavy computation itself. section 9.2.1 section 9.2.2
  • Respecting dependencies declared in the workflow DAG, such as parsing data before augmentation, dataset construction, and training. section 9.2.1
  • Using shared orchestration state while workers exchange task outputs through the object store. section 9.2.2

Dependency-ordered training workflow

A monthly training workflow can define parsing, augmentation, dataset building, and training tasks, then declare each dependency with a directed chain. After submission, the scheduler detects the workflow and dispatches each task in that order. section 9.2.1

Figure 9.5 A design overview for a generic workflow orchestration service

Use the system design to trace how the scheduler and controller connect the web server, metadata database, worker group, and object store. section 9.2.2

How Designing Deep Learning Systems: A guide for software engineers covers it

How deep it goes
Explains scheduling, DAG ordering, dispatch, and surrounding components, but does not detail scheduling algorithms or implementation internals.
Examples
Uses a monthly model-training workflow whose parsing, augmentation, dataset-building, and training tasks form a dependency chain.
What it assumes
Assumes workflow, task, worker, and DAG concepts while showing how dependencies determine execution order.
What you can do after
Evaluate/understand how a scheduler places workflows and tasks within a production orchestration architecture.
How it connects
Connects workflow orchestration with workflow DAGs, controllers, workers, metadata databases, and object stores.

Also explained in

Compare how 12 books explain scheduler →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Designing Deep Learning Systems: A guide for software engineers. The section links point to the parts of the book it draws on.