perf: draw at the display's refresh rate while anything moves

Remove the fixed 60 FPS cap. The render governor caps a parked scene at
60 ticks a second, since Cesium still runs the clock, data sources and update
listeners on every animation frame when it skips the draw, and holds
continuous render while the camera moves (moveStart to moveEnd, with pose
sampling for cameras that drift by rounding errors and never raise moveEnd).
Waits that counted frames (a tracked contact's first position, a shared
follow view, a trail's temporary copy) now count drawn time through
src/time/frameWait.js, so they last the same at any refresh rate.
This commit is contained in:
Sameh Khamis committed 2026-11-15 10:41:36 -08:00
1 parent 8d9c907133
commit 9f4254e962
12 files changed
+380 -16

No files matched your search

+4
View File
@@ -32,6 +32,10 @@ hardware-rendered overlay scenes.
| 3 | 558.527 ms | 1,809.592 ms | 438.8 ms | 60 / 60 FPS | 105.1 MiB |
| Median | 604.849 ms | 1,855.836 ms | 439.5 ms | 60 / 60 FPS | 105.1 MiB |
These frame rates were measured when the globe was capped at 60 FPS. It now
draws at the display's refresh rate while anything moves and ticks at most 60
times a second when parked (`src/renderGovernor.js`).
The initial-settle measurement is the more useful launch reference because it
includes the first visual and data settling window. All three samples reached
the display ceiling during both motion and rest.