rts-performance-smoother

Apply an exponential moving average with a factor of 0.05 to raw frame rate values before displaying them. Store raw and smoothed values separately, and only update the visible text on a throttled 250ms timer rather than every frame.

Accumulate delta time and gate all DOM or overlay text updates to a fixed interval, such as every 250ms. Run expensive string formatting like toFixed(1) only inside that throttled refresh block, never in the per-frame loop.

Use 0.08 to 0.10 for high-responsiveness metrics like frameTime, renderTime, and physicsTime. Use 0.05 for standard FPS readouts and 0.02 for chaotic signals like network ping or memory footprint.

Long-duration spikes distort rolling averages when fed into the same smoothing filter. Route spikes like 40ms GC pauses to a separate spike warning cache that shows a temporary alert while keeping the baseline FPS line stable.

The main anti-patterns are allocating objects inside hot loops, running string formatting every frame, and mutating overlay DOM nodes per frame which triggers layout thrashing. Confine all formatting and UI mutation to the throttled update tick.