mirror of
https://github.com/rcourtman/Pulse.git
synced 2026-10-15 00:22:28 +00:00
rcourtman
b262f24c54
The remaining scroll hitch on large estates was the realtime websocket tick: every few seconds a delta landed mid-gesture and blocked the main thread for 200-560ms. The scroll path itself was already clean after the windowing fixes, so the tick was the one thing still hitting the wheel. Mid-gesture ticks now cost ~1ms: the resource delta queues unapplied in arrival order (even the baseline patch walks the whole estate), and the reporting projection plus the lastUpdate tick token defer latest-wins alongside it. Holding the token matters as much as holding the data — it is what unified resource projections and workload remaps key on, so deferring it keeps every downstream consumer quiescent through the gesture. Everything drains as one coalesced batch at scroll idle, through the same deferral set and flush the hidden-tab path uses. Ordering and lifecycle guards: a non-empty queue keeps queueing so deltas never apply out of order, hidden-tab ticks drain the queue before applying in place, a full snapshot supersedes and clears the queue, and connection resets drop all pending deferral state. Alert application stays live mid-gesture. Verified on the 50-node/929-guest mock estate: zero websocket long frames across 16-20s continuous scrolls (previously one 200-560ms block per tick), one coalesced flush ~300-450ms after gesture end, and the Last refresh footer still advancing on desktop and narrow viewports. This is a scheduling boundary, not a cost reduction: the per-tick reconciliation cost itself remains owned by the resource-payload-static-metadata coverage gap.