← RFC

Routing Control Overhead — Measured Result (INFRA-aggregated DV vs flooded link-state)

Status: Stage 2 result. Date: 2026-06-08. Tag: sim-result-v5. Reproduce: cd sim && python3 -m experiments.routing_overhead (writes routing_overhead.png).

Routing control overhead: flooded link-state above 100% saturation; INFRA-DV near the 40% line

Measures the routing-control claim from routing-options.md / synthesis §4.2: flooded control is O(N²) and fatal at scale, while aggregating control through the few INFRA nodes makes it O(N). Same connected multi-hop mesh; only the control scheme changes. Control airtime is the whole signal, so we read channel offered-load (and per-node utilisation) directly.

Control overhead vs N (LongFast, 60 s interval)

N INFRA flooded link-state (offered) INFRA-DV (offered) INFRA-DV (median node)
20 2 259% 13.1% 12.3%
50 4 764% 30.7% 22.4%
80 4 1171% 51.4% 29.9%
100 4 1441% 61.6% 31.5%

Registration cadence — the tuning knob the analysis named

The analysis says INFRA-DV control is "dominated by registration cadence (the main tuning knob)". Confirmed at N=100, I=4:

Registration interval offered load median node
60 s 59.2% 30.0%
180 s 21.6% 11.7%
300 s 14.6% 7.9%

At a ~3 min registration interval the scheme lands exactly on the analysis' ~20% (→~12%) budget — not by tuning to fit, but because slowing an O(N) term scales it proportionally. (My default 60 s is deliberately aggressive; the design registers in scheduled TDMA slots, so the real contention cost is lower still.)

Honest notes

Bottom line: flooded mesh-wide link-state is unusable past a handful of nodes (collapsed by N=20); INFRA-aggregated distance-vector keeps routing control O(N) and inside the budget, tunable to ~12% via registration cadence — the routing half of the recommended architecture, measured.