perf(android): normalize variable refresh rate and render resolution #1083
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#1083
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
Android devices differ in native resolution, DPI, and variable display refresh rate. Orbital currently configures the surface at the native window size and leaves refresh selection to the platform/compositor. That makes phone/tablet performance captures hard to compare: raw FPS can change because of resolution or refresh before any renderer difference is involved.
This is an Android-platform concern independent of the exact phone/tablet settings.
What is missing
Proposed direction
Acceptance criteria
Concrete Android evidence from the phone capture:
monitor.refresh_rate_mhz: 0 (winit does not provide a usable refresh rate here)AutoNoVsync; supported:Mailbox,Fifo; vsync off; desired latency 2This should therefore include per-row capture fields such as window width/height, surface width/height, orientation, render scale, refresh rate and present mode, plus an Android display-mode/refresh fallback when winit reports 0.
The tablet files submitted with this run are actually phone duplicates (same Mali-G720/1220x2582 metadata; CSV byte-identical to an earlier phone capture), so they are not useful for the tablet comparison.
Tablet evidence added:
monitor.refresh_rate_mhz: 0 (same missing-refresh problem as the phone)AutoNoVsync; supported[Mailbox, Fifo]; vsync off; desired latency 2gpu_complete~567 msThe phone and tablet have different pixel counts and GPU classes, so their raw FPS cannot be compared directly. Matching render resolution and refresh (or at least recording them per row) is required.
Resolution A/B confirms the issue is real and high-impact:
gpu_complete~680 msgpu_complete~204 msThe tablet display reports an active 48 Hz mode (supported 120/90/60/50/48/30), while winit metadata says
refresh_rate_mhz = 0.present_modeisAutoNoVsync; supported modes are Mailbox/Fifo. Thermal status is 0 and GPU is ~40 C, so this is not throttling.This strengthens the request for: