Module windows 

Steady and disturbed time, and the latency and throughput split across it.

The contract’s latency budgets and throughput floors apply to the steady windows only. A window is disturbed from a fault’s injection until its cleanup plus the longest deadline of the recoveries it is measured for: that is how long the contract lets the cluster take to recover, so nothing inside it is held to a steady budget. Everything else, the settle tail included, is steady.

A sample is classified when it is taken, against two sets of spans: the spans the schedule plans, and the spans the faults actually ran, which a slow cleanup can stretch past the plan. While a fault is injected and not yet cleared, every sample is disturbed.

Structs

Latencies

Latency samples split by window, and the acknowledgements that count toward the steady rate.

Span

A half-open interval of wall-clock Unix milliseconds.

Windows

The spans that make time disturbed, shared by every task that classifies a sample.

Functions

measurement

A path’s measurement from its producer’s and consumers’ samples.

planned_span

The disturbed span the schedule plans for fault, for a load that started at load_start_ms.

steady_millis

Milliseconds of load that no span of spans covers.