perf(reporting): record capture environment and timing distributions in performance CSV #1078
Labels
No labels
Context: Bug
Context: Enhancements
Platform: Android
Platform: Linux
Platform: Web
Platform: Windows
Platform: iOS
Platform: macOS
Release
Target: CI
Target: CLI
Target: Dependency
Target: Engine
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
SakulFlee/Orbital#1078
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
The performance CSV is missing the context needed to compare captures across machines:
Without these, Windows and Linux captures differ by 1.5-10x and cannot be normalized. The Windows capture also has no information about resolution or refresh rate.
Timing fidelity
The CSV currently writes per-second averages only.
cdt_msis the last frame's delta, not an average, and short hitches are hidden. Add at least:Suggested shape
PERFORMANCE_REPORTING.md.Acceptance criteria
The tablet capture makes this higher priority: phone
presentis ~89 ms, tabletpresentis ~342 ms, and pre-hybrid FPS was ~130 vs ~60-80. Without resolution, render scale, refresh, and present mode, we cannot tell whether the 3.8x present difference is pixel count, GPU capability, or a swapchain problem.Please record at least resolution, render scale, refresh rate, present mode, and vsync/fps-limit state with each Android capture.
The minimal Android capture shows why debug-UI state must be recorded:
iced_draw~0.05 ms,overlay_layers~1.05 ms.iced_draw~10.4 ms,overlay_layers~15.3 ms.Record at least:
Otherwise two captures from the same device and scene are not comparable.
Expanded metadata list after the minimal-run analysis:
Startup / sidecar:
SHADER_F16), key limitsdesired_maximum_frame_latencyPer frame / per second:
frame_gap/ event-loop wait and frame-limiter waitThis is not meant to be per-frame allocations or per-entity logging; startup + one row per second is enough unless a detail mode is enabled.