demo · v135

Sub-millisecond setInterval, measured

Why this matters — the explainer calls out high-cadence simulations (physics ticks, audio worklets that need their own scheduling, animation interpolators) that used to be capped at ~1 kHz even when the underlying clock could do more. With the clamp removed, setInterval(fn, 0) now actually fires as fast as the event loop can pump. The gauges below measure the observed cadence.

setInterval clamp: removed in 135
ticks observed
0
callbacks fired
avg interval
—
ms between ticks
observed rate
—
Hz

the code

// Before: setInterval(fn, 0) was clamped to 1ms.
// Chrome 135: no clamp — limited only by the event loop.
let last = performance.now();
const id = setInterval(() => {
  const now = performance.now();
  console.log(now - last);   // sometimes 0.2-0.5ms now
  last = now;
}, 0);

see also