Remote FSDB viewing: binary deflated records beat JSON 50x on the wire

Serving FSDB waveform data from a remote host (Verdi FsdbReader via VaporView's node addon) to a local web viewer: the naive JSON reply ([[time,"0101..."],...]) for a 400k-change clock was 5.4 MB (964 KB even with ssh -C) and two 200k-change 32-bit buses were 17.8 MB, 4.7 s end to end, mostly JSON build/parse, not the link (~10 MB/s). Packing changes as VaporView's own record layout ([u64 LE delta time][width value chars]) and zlib deflateRawSync level 1 on the remote side, framing replies as a JSON header line + binLength raw bytes over one persistent ssh stdio channel, and inflating in the browser with DecompressionStream('deflate-raw') cut the clock to 17.6 KB and the buses to 1.27 s. Remaining cost is the addon building one JS string per change; pack in C++ next. Measure link bandwidth first (ssh host 'head -c 20M /dev/urandom' | wc -c) before blaming the network.