diff --git a/quest/m2/cluster-routing/routes/README.md b/quest/m2/cluster-routing/routes/README.md index 4b8d346b48f..26e66f7f560 100644 --- a/quest/m2/cluster-routing/routes/README.md +++ b/quest/m2/cluster-routing/routes/README.md @@ -542,6 +542,7 @@ benchmarks. - [Route layer acceptance](/quest/m2/cluster-routing/routes/acceptance.md) - forwarding fixtures ported and the model deleted, incident fixtures, end-to-end checks, and benchmarks - [Firefox tabs prove their route key](/quest/m2/cluster-routing/routes/browser-proof.md) - a current Firefox tab opens a lite-07 session with a route-key proof the relay verifies, once neqo's exporter follows the draft - [Playwright bundles Chromium's spec exporter](/quest/m2/cluster-routing/routes/playwright-pin.md) - the toolchain's Playwright bundles Chromium 158+, so the route key lane proves the Chromium tab +- [Showing an identity's claims costs the claims that changed](/quest/m2/cluster-routing/routes/show-cost.md) - lite-07 session setup and teardown grow linearly with broadcasts, not quadratically per identity ## Related diff --git a/quest/m2/cluster-routing/routes/show-cost.md b/quest/m2/cluster-routing/routes/show-cost.md new file mode 100644 index 00000000000..2e1867b1886 --- /dev/null +++ b/quest/m2/cluster-routing/routes/show-cost.md @@ -0,0 +1,32 @@ +# [M] Showing an identity's claims costs the claims that changed + +## Goal + +A lite-07 session's setup and teardown cost grows linearly with the +broadcasts it carries, as lite-06's does. One identity holding many claims no +longer makes `show` in `rs/moq-net/src/route/mod.rs` quadratic. The session +bench (`rs/moq-net/benches/session`) and the route bench +(`rs/moq-net/benches/routes.rs`) show it, swept over both axes as the +repository's fan-out rule requires. + +## Plan + +Planned 2026-11-09 (maintainer, /quest-complete follow-up of +[moq-dev/moq#8352](https://github.com/moq-dev/moq/pull/8352)). ✅ m2, in this +epic (rejected: m4, dropping it). + +#8352's session bench measured lite-07 setup at 4096 broadcasts at 4.9 s of +CPU, against 0.5 s for lite-06, and teardown the same. It traced this to +showing one identity's claims: every change re-derives what the identity +shows from all of its claims. That ran on main after +[moq-dev/moq#8293](https://github.com/moq-dev/moq/pull/8293) (routes presented +incrementally), but before +[moq-dev/moq#8374](https://github.com/moq-dev/moq/pull/8374) (a relay folds +received route batches by the claims they change). + +Re-measure on current main first. If #8374 already made it linear, record the +numbers in the PR and delete this quest. Otherwise keep what `show` derives up +to date per changed claim instead of recomputing it, and add a route-bench +case swept over claims per identity and claims changed. + +Public API: none expected. Wire: none.