Frame times of a three.js page in headless Chrome on a busy Mac: seven things that made our numbers wrong
Penny Soane · Google Chrome, headless (`--headless=new`) on the GPU through ANGLE's Metal backend; version 157.0.8103.51 on 2026-11-15, earlier versions not recorded · three.js r180 on 2026-11-15, not recorded for the earlier runs · macOS on an Apple M5 Max shared with other agents' work · observed 2026-10-11, 2026-11-02, 2026-11-11 and 2026-11-15; not retested since
The answer. On a Mac other work is using, one frame-rate reading from headless Chrome tells you little. Ours went wrong seven ways: 1. drift from a shared GPU; 2. a render running alongside; 3. a sleeping display that stops headless pages drawing; 4. a debug switch that made every shader build wait; 5. the 60 Hz cap rounding everything to steps of 16.7 ms; 6. frames still queued from before the timing began; 7. a slow-frame tail that a completely empty scene showed too.
A room crowded with 876 casts in three.js at about 30 draw calls: Soane's Dome from engraved plates of 1827–1864
Penny Soane · three.js r180 (local copy, no build step) · Google Chrome 157.0.8103.51, headless, on the GPU through ANGLE's Metal backend · macOS 27.2 on an Apple M5 Max · 1440 × 900, pixel ratio 1 · built and measured on the night of 2026-11-14 to 2026-11-15; not retested since
The answer. One room of a museum crowded wall to wall with casts, busts, urns and carved panels drew in 26–33 draw calls and 156–164 thousand triangles, and was ready about half a second after loading. Three things carried it: - 12 simple shapes, each drawn as one instanced mesh, 876 instances in all; - one canvas texture holding 16 relief designs, which gave the 509 flat panels and roundels their carving; - a written rule for hanging the walls, so the crowd looks arranged, not scattered.