Files
aevolution/schemas/network/m10-budgets-v2.md
T
dingoandClaude Opus 5.5 1daa62cf6d
Foundation / checks (deploy) (push) Successful in 3m26s
Foundation / checks (ecs) (push) Successful in 1m55s
Foundation / checks (client) (push) Successful in 12m32s
Foundation / checks (network) (push) Successful in 13m34s
Foundation / checks (tsan) (push) Successful in 7m42s
Foundation / checks (checks) (push) Successful in 32m43s
Foundation / checks (postgres) (push) Successful in 46m18s
Foundation / postgres-tools (push) Successful in 17s
Foundation / image (push) Successful in 2m28s
Foundation / server-image (push) Successful in 4m5s
M10.9: raise the evo-server session cap to 2000 and close 10.9 for now
Maintainer decision (2026-10-09): the region session cap becomes a safety bound of 2000
(plus 64 connections of headroom); the load governor is the working limit. Library bounds
go from 1024 to 4096 in SessionControl, IntentAdmission and ReplicationServer (defaults
stay 32). Drills stop for now: saturation and native-client observation move to a later
2k drill, whose prerequisites ADR-0097 lists (single-thread CPU, region login rate,
256 MiB pod limit, linear lookups). Declared: >= 32 sessions within every budget on the
reference worker. Budgets v2, STATUS, ROADMAP, VALIDATION. Refresh the dev session window.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-09 08:22:04 -04:00

4.2 KiB

M10 timing and workload budgets, version 2

Version 2 (2026-10-08, maintainer decision in M10.9d, ADR-0097) changes one row: per-tick region work. The first evolution-dev reference runs showed the host's synchronous commit flush alone reaching 23-25 ms at p99 with no session, about once per second, while other ticks stayed near 3.5 ms. Work is now bounded at p95 over all ticks, plus a separate bound for ticks that commit a batch. Moving the commit I/O off the simulation thread is a recorded follow-up (a persistence/ADR change), not part of M10. Affected: the load drill's summary (tools/ops/load-drill.sh) and the governor documentation; the governor itself already acts on p95. Version 1 is kept for history.

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; cap 2000 in evo-server (maintainer, 2026-10-09; library bound 4096). The load governor is the working limit: within every budget to 32 on the reference worker (fifth run); saturation is unmeasured (2k drill pending) budget 10.9
Per-tick region work p95 <= 25 ms over all ticks on the reference worker; ticks that commit a batch <= 50 ms (measured separately) budget (v2) 10.9 (m10 load-report commit_max_us / other_max_us, 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).