docs(research): #59 MTU/FEC-rate investigation findings + measurement tools#94
Merged
Merged
Conversation
…measurement tools Measure-first spike on #59 (throughput lever 4c). Findings doc records the send-path overhead model, two bounded MTU levers, the wire-padding constraint (every FEC symbol is zero-padded to full symbol_size on the wire), and the FEC-rate experiment showing the Default-class repair floor is load-bearing (decaying it to 0 regressed low-rate lossy recovery 10/10 -> ~7-9/10) rather than waste. Plus two reusable bench examples (mtu_symbol_sweep, fec_rate_experiment).
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Preserves the measure-first investigation of #59 (throughput lever 4c) as durable institutional memory. No production code — a research doc plus two reusable bench examples alongside the existing
pipeline_profile.Why
The #59 spike found both "cheap wins" are illusions once measured, and that's worth recording so the next person doesn't re-litigate it. Full analysis:
docs/research/2026-07-22-mtu-packetization-findings.md. Headlines:symbol_sizeon the wire (fec.rs"last zero-padded"; reassembler rejectsdata.len() != symbol_size; framer sends it untrimmed). So a blindsymbol_sizeincrease is a bandwidth regression for small packets.symbol_sizeto ~1500 helps only per-symbol costs and only for packets that currently split; jumbo inner MTU helps everything but only where the whole path carries jumbo. The issue's "reduces every per-packet cost proportionally" holds only for the jumbo lever.min_ratiofloors at 0.10. Tempting to decay it to 0 — but the experiment measured the cost: clean-link datagrams halved (2.000 → 1.000), but 10% netem low-rate ping recovery regressed 10/10 → 7/10, 9/10, 8/10 (sparse traffic can't keep the controller armed; losses go unrecovered). The floor protects exactly the low-rate latency-sensitive traffic the class exists for. Change rejected.Contents
docs/research/2026-07-22-mtu-packetization-findings.md— the full write-up.crates/yip-bench/examples/mtu_symbol_sweep.rs— symbols/packet + outer bytes across inner-size × symbol_size (realTransport::encode).crates/yip-bench/examples/fec_rate_experiment.rs— whether the Default class decays on a clean link.No behavior change;
#59updated with the same conclusion.