Performance Dashboard¶
This page surfaces the current published benchmark snapshot and the suite lanes that are expected to grow it.
Charts use assets/data/benchmark_latest.json generated during docs build.
The current public dataset contains one committed result row, and the coverage table below shows the user-relevant benchmark lanes already defined in the suite.
Current Public Snapshot¶
| Lane | Purpose | Score | Avg FPS | P99 Frame (ms) | GPU Time (ms) |
|---|---|---|---|---|---|
static_baseline |
Low-noise raster baseline | 90.7 | 74.0 | 15.62 | 0.0 |
The snapshot above is the current committed public result. It is the reference row used by the charts below until more published scenarios are added.
Coverage Map¶
| Lane | Purpose | Status |
|---|---|---|
static_baseline |
Low-noise raster baseline | Published in benchmark_latest.json |
streaming_corridor |
Camera sweep stressing chunk turnover | Defined in the benchmark suite, not yet published |
city_flyover |
High-altitude visibility-change stress | Defined in the benchmark suite, not yet published |
instance_storm |
Many-instance submission pressure | Defined in the benchmark suite, not yet published |
lighting_stress |
Animated light and shading stress | Defined in the benchmark suite, not yet published |
unified_composite |
Integrated all-systems composite lane | Defined in the benchmark suite, not yet published |
Lane Scores Overview¶
Frame Timing¶
How to Update¶
- Run a benchmark:
python tests/runtime/run_benchmark.py --profile everything - Export data:
python scripts/export_benchmark_vegalite.py - Update the current snapshot table above when the published lane set changes.
- Build docs:
python scripts/build_docs_site.py --strict
See Benchmark Suite Runner for full benchmark documentation.