| |
|
|
|
|
| |
each link, measured: a session on a directory and two shells (here, or on the FreeBSD box over ssh), terminal clients in a pty kept by pyte and offscreen window clients through their test feed, each a seeded monkey of moves, edits, undo, saves, Looks, pickers, shells with programs, panes and columns, clicks, the wheel, the pointer resting, pastes and idle gaps, beside resizes, detaches and attaches, an Upgrade and a script's 9P edits; its table a client (rejoins, checks that differ, exits and cores, freezes at quiet points, a terminal client's screen and cursor against the session's render of its view, visible rollbacks, keystroke to output or frame p50/p99) and the session's worst boundary, exit 1 on any breach; test/delay_relay.py takes --jitter (order kept)
Co-Authored-By: Claude Opus 5.5 <[email protected]>
|
|
|
held a fixed delay from its arrival each way, in order, with an optional rate cap
It accepts on a Unix or TCP socket and connects each client on to another; each direction is a reader that stamps every chunk with its due time (its arrival plus the delay, or, capped, the moment the link has carried the chunks before it plus the delay) and a writer that sends it then, so a stream's throughput is not serialised behind the delay. 15, 40 and 103.5 ms one way are the gates' 30, 80 and 207 ms RTTs (the last the FreeBSD box's). ponytail: the buffer is unbounded, a link of infinite bandwidth-delay product; ssh's own window is what bounds a real one.
`--self-check` measures what it adds against an echo and a sink: an RTT 0.26 to 0.56 ms over the two delays (the threads' wake-ups; the low end pinned to two quiet cores), 2.3 to 4.3 GB/s through it at every delay (256 MiB, against 9.9 to 12.4 GB/s direct), and a 20 MB/s cap held to 19.99.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
|