REAL-TIME · CANVASInterface Experiment
Thousands of events a second land as one readable screen: the worker aggregates, the main thread only draws.
/ About
ReactTypeScriptWeb WorkerCanvas
A firehose pushes thousands of events a second: React can't re-render that fast, and no screen can show every event. The socket runs in a Web Worker, so the flood never touches the main thread. The worker aggregates, the main thread only draws from 10Hz snapshots.
What it explores
01
Ingest in a worker so parsing never blocks the UI: failover, time-cursor resume, gap markers on disconnect.
02
Backpressure: a 1-in-M parse gate on processing lag, hysteresis-guarded so sampling doesn't flap.
03
Render without React: snapshots land in a ref; each panel's rAF loop writes canvas/DOM directly.
04
Under overload it samples down and shows the loss on the HUD, never hides it.