Run the benchmarks

The same project the published numbers come from, built to WebAssembly. Pick a case, watch it build, and read the median tick beside what rapier took inside it.

Needs WebGPU. The heavier cases build ten thousand bodies and take a few seconds before they settle.

What these numbers are, and are not

They are the browser's. A web build is single-threaded, so the solver that runs on seven threads on a desktop runs on one here, and the browser paces frames to the display rather than to a fixed tick. Read them as this machine in this tab, and take the published table for the comparison against Godot: those come from a headless run at a fixed 60 Hz on a quiet machine, beside the Godot physics suites measured the same day.

Everything else is the same engine: the same scenes, the same rapier, the same scripts. Each case reports a whole physics tick, rapier’s own step inside it, and what the case’s script cost crossing the seam — all read from engine.timings(), the profiler the editor’s own dock draws.

To run it on your own machine, where the numbers mean something: balaur run examples/benchmark --headless --fixed-tick -- --case=3d/pyramid, or open it in the editor and press a case.