You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add opt-in ?perf=1 timing panel to Interactive Explorer (#118)
First step of the "progressive globe as reference design" strategy:
ground performance work in numbers before optimizing.
Instruments three natural hook points with performance.mark():
- duckdb_init (DuckDBClient.of() call)
- viewer_init (Cesium.Viewer construction)
- first-globe-frame (first scene.postRender callback)
A new perfPanel cell reads these marks plus the browser's paint
entries and the existing p1/r{res} measures, and renders a small
fixed panel in the bottom-right. Gated on ?perf=1 — off by default
in production. Also dumps to console.table for CI capture.
Baseline (local, headless Chrome, warm R2):
- first-paint 370 ms
- duckdb_init 1.47 s
- nav → viewer ready 2.59 s
- nav → phase 1 complete 6.57 s
Next optimizations to drive against these numbers: preload critical
parquets, DuckDB init off main thread earlier, R2 cache header audit.
Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>
0 commit comments