What changed in 0.3.0
Two numbers this tool prints were wrong. Both are fixed, and both mean a result
from 0.2.x cannot be compared with one from this release.
Your upload figure was about a fifth too high. The throughput window and the
byte count disagreed: bytes were counted from the moment the upload started,
including a 1.5 second ramp, and then divided by a window with that ramp
subtracted. So the numerator covered roughly 8.3 seconds and the denominator
6.8. It was found by running speedtest on the same line in the same
afternoon — 284 Mbps against our 502 — because the code was self-consistent and
the number it printed was plausible, so no amount of re-reading would have shown
it. Both now measure the same window, and the ramp is excluded from each, which
is also the better measurement: TCP slow-start lives in there.
If you ran an earlier version, the added-latency figure was always fine. It
is the number worth having and it was never affected.
"Launch records" were never launches. Steam keeps one timestamp per title,
so the hour-of-day histogram held one sample per game — at the hour it was last
closed, across your library's whole life. A game you play nightly counted once,
and so did a game you tried once and abandoned, which means the shape
over-weighted trying and under-weighted playing. It now says what it is,
shows how far back the samples reach, and draws a second histogram over titles
you have actually played in the last 30 days when there are enough of them to
say anything.
nesdoctor
Checks whether your machine can host a Nestri box,
and measures what your connection actually does under load.
Nothing is uploaded. There is no server to upload to: the network
test talks to Cloudflare's public speed-test sink and to 1.1.1.1,
neither of which is ours. The output is a line on your terminal that
you may choose to paste somewhere.
Download the file for your platform, verify it against
SHA256SUMS, and run it. On macOS and Linux you will need
chmod +x first. Source is in apps/nesdoctor.
The Intel macOS binary is cross-compiled and is the one target CI
cannot execute to test. Every other binary here was run by the
workflow that built it.
The number worth running it for is added latency under load.
Everybody knows their download speed; almost nobody has seen this
one, and for anything interactive it is the figure that decides it.
Full Changelog: nesdoctor-v0.2.2...nesdoctor-v0.3.0