Expand description
Per-server latency, speed and reachability, and the one-word status the list shows.
One row per server, no history: latency and speed are exponentially weighted averages, the last few upload speeds ride along as a short array for a sparkline. The footprint does not grow with use.
Latency is the BUD-06 preflight round-trip — a small request, so it is dominated by distance and server load and comparable between servers. Speed is this device’s throughput to the server, which the uplink caps: shown as a number, never graded.
Structs§
- Sample
- One recent upload: its speed and its size, stored as
[mbps, bytes]. Rows written before sizes were kept hold a bare number and read back withbytes: 0. - Server
Stats - Server
Status - The list’s one-word answer to “will my next upload here work?”.
Constants§
- FAIL_
MAXED - FAIL_
OFFLINE - MIN_
SPEED_ SAMPLE_ BYTES - Below this an upload is all round-trip and says nothing about throughput.
Functions§
- derive_
status - Pure: what the list should say, from what is known.
infois the server’s document when it has one;statsthis device’s history. - migrate
- record_
failure kindisFAIL_OFFLINEorFAIL_MAXED.- record_
latency - A small request answered in
ms. - record_
ok - The server answered, whatever it said: it is reachable.
- record_
upload bytesaccepted inms. Small uploads are ignored: they measure the round-trip, not the pipe.- stats_
for - status_
for