With the perf benchmark now waiting for the surface the map was drawn on,
headless Chromium showed what WebGL costs without a graphics card: its
SwiftShader renderer spends about 8 µs per instance, so the coastlines alone
(29k segments, twice) took about 480 ms and a big map 1.4 s a frame, where the
2D canvas takes 46 ms. Players get the same with a blocked driver, a virtual
machine or Mesa's llvmpipe. glInit() now reads the renderer first and keeps
the 2D map on SwiftShader, llvmpipe, softpipe, lavapipe, WARP or any
"software" renderer; GLX.soft lets the GPU benchmark measure them anyway.
- A trial now ends before the next starts: the clock stops, the frame
callback is cancelled (and a queued one turned away), a day still in the
route worker is waited for (or dropped), the clock's leftovers are cleared,
and every trial starts from the same random numbers.
- The renderers take turns going first, scenario by scenario; ?reps=N runs
each N times and reports medians.
- draw() is labelled as CPU submission time; the card's own time comes from
EXT_disjoint_timer_query_webgl2 where available (read frames later, never
waited for, disjoint results dropped); a run drawn by the other map is
flagged.
- npm run perf --browser reads its sync pixel back from the surface the map
was drawn on (the WebGL canvas waits for the card) and says which map each
version drew with.
- Sea, land, waves, clouds, cables, tubes and packets are drawn by the
graphics card; the land is geometry built once, so panning and zooming
repaint nothing.
- Cities, labels and markers are painted once into a sprite atlas and drawn
in one call (with drawImage in 2D, which speeds up the 2D map too).
- Settings > Map drawing: Auto or Always 2D, per device. Browsers without
WebGL2, a lost context and puzzles keep the 2D map.
- npm run bench:gpu compares 2D and WebGL in a real browser on a real GPU;
?fps shows a frame meter.