Skip to content
Merged
2 changes: 1 addition & 1 deletion quest/m2/cluster-routes/acceptance.md
Original file line number Diff line number Diff line change
Expand Up @@ -38,7 +38,7 @@ router's forwarding and operation-count fixtures went with it, and
`route/tests/multicast*.rs` covers the new one. The route fan-out quest
those pinned was deleted
with the old rule, its one surviving cost moved to
[route benches](/quest/m3/route-benches.md).
[route wakes](/quest/m4/route-wakes.md).

Decided 2026-11-16 (maintainer, /quest-plan of the pre-cut audit): the
switch makes `origin::Config::update_hold` crate-private, since nothing
Expand Down
1 change: 0 additions & 1 deletion quest/m2/multicast/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -38,7 +38,6 @@ children, [the uncovered cases](/quest/m2/multicast/accept.md),
[route layer acceptance](/quest/m2/cluster-routes/acceptance.md) retiring
the lite-06 mitigations. After the cut come warmth's wire
([cache-aware routing](/quest/m3/cache-routing/README.md)),
[route benches](/quest/m3/route-benches.md),
[the proof binding](/quest/m3/route-proof-binding.md),
[route health](/quest/m3/route-health/README.md), and
[outbound federation](/quest/m3/cluster-routing/federation.md).
Expand Down
13 changes: 8 additions & 5 deletions quest/m2/multicast/mesh-replay.md
Original file line number Diff line number Diff line change
Expand Up @@ -34,10 +34,13 @@ to the tests that exist:
newest and previous release meshed, and lite-07 is chosen link by link:
only two new relays speak it to each other. Nothing runs a mesh in that
state, where one path crosses both versions.
- The same decision keeps the per-broadcast rewrite of
[route benches](/quest/m3/route-benches.md) in m3 on the condition that it
is measured on a deployed mesh's shape before that mesh's cluster links
move to lite-07. This quest's report is that measurement.
- The same decision kept the fix for the per-broadcast rewrite after the
cut, now in [route wakes](/quest/m4/route-wakes.md), on the condition that
the cost is measured on a deployed mesh's shape before that mesh's cluster
links move to lite-07.
[moq-dev/moq#9114](https://github.com/moq-dev/moq/pull/9114) benched it:
10 origin writes per broadcast when an upstream reopens twice. This
quest's report is that measurement on a real mesh.

Decided 2026-11-18 (maintainer, on
[moq-dev/moq#9110](https://github.com/moq-dev/moq/pull/9110)): ✅ it blocks
Expand Down Expand Up @@ -69,7 +72,7 @@ Public API: none. Wire: none.

## Related

- [Route benches](/quest/m3/route-benches.md) - the costs this measures on a real mesh
- [Route wakes](/quest/m4/route-wakes.md) - owns the rewrite this measures on a real mesh
- [The cases no test covers run on real sessions](/quest/m2/multicast/accept.md) - the same failures on mock sessions with mocked time
- [Random fault schedules](/quest/m4/cluster-fault-schedules.md) - searches fault timings on the simulated clock
- [A nightly soak](/quest/m4/relay-soak.md) - one real relay under churn
7 changes: 3 additions & 4 deletions quest/m2/multicast/route-counters.md
Original file line number Diff line number Diff line change
Expand Up @@ -37,9 +37,9 @@ Agent's choices, for the implementer to revisit:
- Count in `rs/moq-net/src/stats.rs` beside `routes_refused`, per label and
never per broadcast or per node, so the cost and the output stay flat as
the mesh grows.
- The count of broadcasts rewritten is the cost
[route benches](/quest/m3/route-benches.md) measures, read from a running
relay.
- The count of broadcasts rewritten is the cost the `routes/reopen` bench
measures and [route wakes](/quest/m4/route-wakes.md) owns, read from a
running relay.
- Say what the announce counters mean on a lite-07 session, where a route
change is no longer one announce per broadcast, and fix the doc or the
counter if they now mislead.
Expand All @@ -49,5 +49,4 @@ shared role. Wire: none.

## Related

- [Route benches](/quest/m3/route-benches.md) - measures the rewrite these count
- [Real relays replay a mesh and its faults](/quest/m2/multicast/mesh-replay.md) - reads these in its report
51 changes: 0 additions & 51 deletions quest/m3/route-benches.md

This file was deleted.

37 changes: 25 additions & 12 deletions quest/m4/route-wakes.md
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
# [M] A route change wakes only the fronts it affects
# [L] A route change writes once and wakes only the fronts it affects

## Goal

Expand Down Expand Up @@ -37,9 +37,27 @@ Facts from `main` (`rs/moq-net/src/model/origin.rs`, since Wildcard landed in
exactly the path skips both hashes. A join moves only paths the newcomer
wins, a leave only paths the leaver was winning.
- On lite-07 the route layer writes into this table through `route::node`,
one write per broadcast whose way changed; a change to one route rewrites
every broadcast behind it, which [route benches](/quest/m3/route-benches.md)
owns. This quest is the fronts' half: what each write wakes.
one write per broadcast whose way changed; a change to one route's cost
rewrites every broadcast behind it (`route::node` `State::flush` relanes
each, and `Served` carries the cost). This quest owns both halves: one
shared record per route in the origin that its broadcasts refer to, so a
re-price is one write, and what each write wakes. `routes/reopen/spare`
measures the route side (moq-dev/moq#9114): an upstream reopening twice
in a row costs 10 origin writes per broadcast behind it, 2.8 s at 16
routes of 4,096 broadcasts, linear in each axis; `routes/drain` costs 2
per broadcast, 480 ms at the same shape. A route that moves to another
path at the same rank through the same session already rewrites nothing;
one that moves to another session at the same rank relanes every
broadcast its node claims.

Decided 2026-11-18 (maintainer, on
[moq-dev/moq#9114](https://github.com/moq-dev/moq/pull/9114)): ✅ the origin
record lives here, in m4 (rejected: moving this quest to m3; a separate m3
quest for the record alone). It replaces that morning's decision to keep it
in m3 with the benches. The measured cost above is about 4 µs a write, so
the worst flap seen on a deployed mesh costs one relay a fraction of a
second, and [the mesh replay](/quest/m2/multicast/mesh-replay.md) measures
it on that mesh's graph before its links move to lite-07.

Decisions:

Expand Down Expand Up @@ -79,10 +97,9 @@ Decisions:

Decided 2026-10-13: coordinate the index with the route model and per-track
active/standby selection. Do not build a second route table per track or
turn one route's cost change into per-broadcast mutations. Whichever
implementation lands first, this or the origin record in
[route benches](/quest/m3/route-benches.md), preserves these operation-count
tests for the next.
turn one route's cost change into per-broadcast mutations. The origin
record and the index land together here, keeping these operation-count
tests.

Verification: `origin/pool_churn` leaves flat in served paths at every pool
width it already sweeps, and a unit test that counts `select` calls per
Expand All @@ -95,7 +112,3 @@ Public API: none. Wire: none.
## Required

- [Cache-aware routing](/quest/m3/cache-routing/README.md) - adds the warm pick to how a relay chooses its source, so the index is built once on the final selection

## Related

- [Route benches](/quest/m3/route-benches.md) - the route layer's side: one origin record per route instead of a write per broadcast
Loading