A backup that finishes on a slow line

A snapshot sent over a home uplink that gives the backup 1 to 2 Mbit/s used to fail every time: each put got a deadline from a fixed 5 Mbit/s floor (66 s for a 4 MB chunk), eight puts shared the line, and the run retried from the top (#13743). Now:

rate the line has actually landed puts at, over its share (src/snapshot/line.ts, withRetries in src/snapshot/store.ts). It is the put's own, never what is left of the run. A put that moves nothing still times out.

has been measured (putsAtOnce).

sealed lane, under their hidden names) and sends only the rest, so a killed run resumes without re-sending; this was already true of the sealed lane and is now tested.

and the backup.progress event say bytes sent, "N of M chunks already there", bytes to go (estimated from the last snapshot's size), the rate and when it will be done.

Tests: test/snapshot-slow-line.test.ts.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs