cadence-bench

A real-time audio path hands the transport a 20ms frame every 20ms. The loop almost everyone writes first sleeps a period after each frame's work, and it cannot hold that rate: every tick it falls behind by however long the work took, and it never catches up. It sounds like occasional choppiness under load, and it does not reproduce on an idle laptop.

This page measures your browser.

Unlike its sibling benchmarks, cadence-bench is a measurement, not a simulation, so the machine running it is the subject. Here that is the Go harness compiled to WebAssembly, in a Web Worker, on a single thread, sleeping on setTimeout and reading performance.now. The absolute figures describe this browser. For Go on real servers, see the published results from Linux, macOS and Windows. The ordering of the strategies is what carries over.

1. What this browser's clock can support

1 core ยท not cross-origin isolated (coarsened clock)

Run a measurement to see each strategy's lateness, tick by tick.