Task scheduling benchmark diagrams

Task scheduling benchmark

Start with how the application begins, then follow data between its folders. Open an operation to see its decisions, calls, failures and cleanup. Its explanation supplies the exact contract and linked dependencies.

This view includes 2 application source files. Package and interface boundaries show checked contracts; their runtime implementations are not expanded. The views describe the checked program, not desired requirements or a recorded execution.

Where execution begins

Startup

It sets iterations to 2000. It sets index and checksum separately, each to 0. While index is less than iterations, within a task and ownership scope, it sets first to a child task running compute with value from index with its inputs captured now. It sets second to a child task running compute with value from index plus 1 with its inputs captured now. source

It reads the result of waiting for first and second in input order; propagate failures once and binds [0] as left and [1] as right. It sets checksum to (checksum plus left) plus right. On leaving this scope, join its child tasks and release its local values. It increases index by 1. source

After the loop, it prints checksum. source

Data flow

100%

Mermaid source

flowchart TD
    n0["Startup"]
    n1["operations"]
    n0 -->|"compute(value) → int"| n1

Follow the data

Each row opens the complete operations and call sites behind one pair of logical units. A grouped arrow records calls between those units; connected arrows need not belong to the same execution path.

From	To	Operations	Read
Startup	operations	1	Inputs, results and call sites

Data crossing these boundaries (1 contracts)

Startup → operations

1 operation, 2 sites

compute

Inputs: value: int. Result: int.

Caller or entry	Evidence
Startup	Call site · Caller explanation
Startup	Call site · Caller explanation

Open a module

Module	Read
main.aug	Flow and sequences · Explanation
operations.aug	Flow and sequences · Explanation

These are static call boundaries, not a request trace. Interface implementations and foreign internals stop at their checked contracts. Dotted arrows defer a callback or browser action. Imports alone do not imply a call.