diff options
| author | Luke Hoersten <[email protected]> | 2026-06-20 10:30:24 -0500 |
|---|---|---|
| committer | Luke Hoersten <[email protected]> | 2026-06-20 10:30:24 -0500 |
| commit | 496da49dd5ce4a3bfc4b5df84ce5c7f7bdbcf504 (patch) | |
| tree | 1aecd053ebf9d82f1e23037cb992dad1c0def64f /sdkconfig.defaults | |
| parent | cebd60d4be74ddac9c18a7b08eef9ec00cbc31f5 (diff) | |
"paint the latest, drop the rest" — FIONREAD skip + Scrypted backpressure-blind + lwIP TCP window bump
Three changes that work together to make the stream "always paint
what's freshest, never sit on a stale frame":
#1 — Firmware FIONREAD skip in stream_server
Right after the body of frame N comes off the wire (and before we
unlock the decoder + spend ~6ms on decode + paint), check the
kernel receive buffer with ioctl(FIONREAD). If at least one more
header (8 bytes) is queued, frame N is no longer the freshest
possible — skip its decode + paint and loop back to read frame
N+1. The TCP recv cost is unavoidable (bytes still have to cross
the wire) but the decoder + paint cost is saved on every superseded
frame. Glass-to-glass latency on the latest frame drops by however
many frames had backed up.
#2 — Scrypted: keep writing past kernel-buffer backpressure
Previously: when sock.write() returned false we dropped the next
ffmpeg frame at source. New: we keep writing through. Node buffers
internally; under our load (~16 MB/s ffmpeg → ~5-7 MB/s firmware)
the buffer rarely exceeds a frame or two. With the firmware now
silently skipping decode on backed-up frames (#1), excess frames
get shed for free on the device side. Scrypted's job is just to
hand the firmware the freshest bytes as fast as possible.
socketBackpressured is still tracked for the diagnostic log.
#3 — lwIP TCP window bump (revisiting earlier regression)
The previous attempt at LWIP_TCP_WND_DEFAULT=32k regressed under
HTTP because every /frame opened a fresh socket and we paid the
slow-start cost repeatedly. The streaming pivot eliminated that:
the socket is long-lived, slow-start runs exactly once, then we
ride the full window for the rest of the session. Bumping to
65535 (max for stock lwIP), SND_BUF to match, RECVMBOX to 16, SACK
on. Expected: recv throughput ceiling moves up from ~5.3 MB/s,
which directly raises the fps ceiling (recv is currently 37ms of
the 43ms per-frame total).
Diffstat (limited to 'sdkconfig.defaults')
| -rw-r--r-- | sdkconfig.defaults | 19 |
1 files changed, 12 insertions, 7 deletions
diff --git a/sdkconfig.defaults b/sdkconfig.defaults index 4c50a23..1ba8375 100644 --- a/sdkconfig.defaults +++ b/sdkconfig.defaults @@ -29,13 +29,18 @@ CONFIG_LWIP_IPV4=y CONFIG_LWIP_IPV6=y CONFIG_MDNS_MAX_INTERFACES=1 -# TCP receive-window tuning attempted (WND/SND_BUF=32k, RECVMBOX=16, -# SACK on). Measured net-negative on the /frame path: ttfb regressed -# from ~350µs to ~1.2ms, body unchanged, and periodic 250+ms stalls -# appeared. Reason: Scrypted's per-frame fetch() opens a fresh TCP -# socket each time, so the larger window just slows slow-start. -# Reverted; revisit once we switch to HTTP keep-alive on the Scrypted -# side. Keeping the lwIP defaults. +# TCP receive-window + buffer tuning. Earlier attempt under HTTP +# regressed because every /frame opened a fresh socket and we ate +# the slow-start cost repeatedly. Under the streaming pivot the +# socket is long-lived: slow-start happens once, then we run with +# the full window for the rest of the session — which is exactly +# the workload these knobs are designed for. Larger WND lets the +# sender keep more bytes in flight per ACK and pushes our recv +# throughput ceiling up from ~5.3 MB/s. +CONFIG_LWIP_TCP_WND_DEFAULT=65535 +CONFIG_LWIP_TCP_SND_BUF_DEFAULT=65535 +CONFIG_LWIP_TCP_RECVMBOX_SIZE=16 +CONFIG_LWIP_TCP_SACK_OUT=y # HTTP server CONFIG_HTTPD_MAX_REQ_HDR_LEN=1024 |
