ADR-0097. evo-load runs bots on worker threads, each a RegionSessionClient with its own account and an in-process dev grant: one intention per tick at its input lead with marker prediction, actions every 2 s, interest moves every 10 s, and re-login after any close. Stepped ramps report pooled and per-client distributions (response, receipt, outcome, login, prediction error), snapshot rate, gaps and bandwidth, drops, failed logins and refusals, generator CPU, a starvation check among connected bots, a budget verdict and the region's evo_m10_* gauges, ending with the sustainable bot count. A Postgres process smoke runs 4 then 8 bots against a real evo-server. Fixes found while ramping: the process fixture's short pumps never read (a chatty child blocked on its stdout pipe), and the load governor refused on a single tick of debt (now 2 refuse, 4 shed). Refreshes the dev session window. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
3.2 KiB
M10 timing and workload budgets, version 1
Normative table for ADR-0089. "Ratified" values were decided by the maintainer (2026-10-03); "budget" values are engineering limits derived from them and from the M10.1 traces and change only with measurements and an ADR-0089 amendment. Version 1 applies to all M10 segments; a change bumps the version and lists affected tests. None of these values is a biological or game rule. Exception to note: genome v1 and metabolism express rates per tick, so the tick quantum currently fixes biological rates in real time; changing it requires a versioned rules migration (ADR-0089).
| Item | Value | Kind | Enforced/tested in |
|---|---|---|---|
| Authoritative tick quantum | 50,000 us (20 Hz) | ratified | checkpoints (tick_microseconds), region host |
| Commit flush | 1,000 ms | ratified | region host flush_interval |
| Final outcome delivery | p95 <= 1.5 s after admission (dev/stage, nominal network) | ratified | 10.4, 10.9 |
| Responsiveness (input -> first reflecting snapshot) | LAN p95 <= 150 ms; 100 ms RTT p95 <= 250 ms | ratified | 10.6, 10.9 |
| Reference hardware | server: one RKE2 worker (8 vCPU, 31.3 GiB) per region host; client: low-spec VM (M9.8g) | ratified | 10.9 |
| Input scheduling window | server_tick + 1 ..= server_tick + 8 ticks | budget | 10.4 admission |
| Client input lead | ceil((rtt/2 + jitter)/50 ms) + 1, clamped 2..8 ticks | budget | 10.4, 10.6 |
| Late input | rejected, never rewound | budget | 10.4 |
| Snapshot cadence (in interest) | every tick | budget | 10.5 |
| Baselines retained | server <= 4 per session, each <= 40 ticks old; client <= 2 | budget | 10.5 |
| Intention sequence | u64 per session, from 1, strictly increasing, no wrap | budget | 10.4 |
| Tick, baseline id | u64, no wrap | budget | 10.4, 10.5 |
| Realtime packet sequence | serial-number arithmetic >= 16 bits, window < half space | budget | 10.2 |
| Session id / epoch | u64 server-assigned, bound to connection; epoch on every message; stale closes | budget | 10.3, 10.4 |
| Intentions per session | 1 per tick (8 per 8-tick window, every attempt counted) | budget | 10.4 |
| Unresolved intentions per session | 256 | budget | 10.4 |
| Realtime datagram payload | <= 1,200 bytes | budget | 10.2 |
| Reliable frame | <= 64 KiB | budget | 10.2 |
| Replication per session | <= 16 KiB per tick | budget | 10.5 |
| Client event queue | 1,024 events | budget | client session |
| Heartbeat / liveness / handshake | 1 s / 5 s / 5 s | budget | 10.2, 10.7 |
| Sessions per region | >= 20 required, 32 default | budget | 10.9 |
| Per-tick region work | p99 <= 25 ms on the reference worker | budget | 10.9 (measured: evo_m10_tick_work_*, ADR-0097) |
| Session handling | <= 0.5 ms per session per tick | budget | 10.9 (measured: evo_m10_session_work_*, ADR-0097) |
| Host input queue | 64 inputs, 64 KiB | budget | region host |
| Overload response | shed interest, refuse new sessions before tick debt | budget | 10.9a load governor: refuse at p95 >= 15 ms or debt >= 2, shed at p95 >= 20 ms or debt >= 4, relax below 10 ms after 5 s (ADR-0097; provisional until 10.9d) |
Determinism: authoritative state is exact given the checkpoint and committed per-tick inputs; timing, delivery, prediction, interpolation and presentation are tolerant (ADR-0089).