diff options
| author | eunhhu <[email protected]> | 2026-09-29 09:49:35 +0100 |
|---|---|---|
| committer | eunhhu <[email protected]> | 2026-09-29 09:49:35 +0100 |
| commit | 17e54aaa3b08f62d9a5488656d5ef8668d76e571 (patch) | |
| tree | d34f1154f0c5576832850ad26498c49b106faa9b /docs/research/079-lent-views.md | |
| parent | 04fa30f5a321f3ce468e02f74851ebb6f795344e (diff) | |
| download | pure-17e54aaa3b08f62d9a5488656d5ef8668d76e571.tar.gz pure-17e54aaa3b08f62d9a5488656d5ef8668d76e571.zip | |
Pace a link's packets, and keep Reno's pace by time as well as by acknowledgments
Packets go at the window an RTT, a quarter more (twice in slow start),
up to 2 ms of it at once (10 to 256 datagrams, RFC 9002 7.7); the sender
says when the next may go. The Reno-friendly estimate grows by the
acknowledgments (RFC 9438) or by time (RFC 8312), whichever is ahead, so
a link its app holds back to a few records a second does not fall
behind it.
In the M6 simulator (RTT 100 ms, 5% loss, 50 records a second) the
median time a record takes falls from 134 to 51-71 ms and the p99 from
about 900 to 290-350 ms; a backlog with 1% loss at RTT 20 ms goes at
8.3 Mbit/s. The transport's CPU a record is unchanged.
Diffstat (limited to 'docs/research/079-lent-views.md')
0 files changed, 0 insertions, 0 deletions