perf(android): Adreno 810 tablet is volumetrics-bound at ~162 ms #1089
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#1089
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
After the light-range fix (
b7086621), the Adreno 810 tablet is no longer deferred-bound. It is volumetrics-bound:gpu_scene_totalgpu_deferredgpu_light_cullinggpu_volumetricsgpu_tonemapgpu_aagpu_volumetricsis ~74% of the frame time. The phone’s volumetric cost at 1220x2582 is only ~12 ms, so the tablet’s ~162 ms is ~13× higher despite only ~1.3× the pixel count.The tablet A/B against
5be0937dconfirms the range fix helped there too (deferred 76.43 → 16.02 ms, scene 100.13 → 38.40 ms, FPS 3.0 → 4.5), but the volumetric pass remains the new bottleneck.Likely contributors
VolumetricQuality::Lowwithmax_distance: 30. Adaptive depth slicing raises the froxel grid to 192 slices, giving roughly 213×133×192 ≈ 5.4M froxels on the tablet.gpu_volumetricscurrently aggregates inject + temporal accumulate + composite; the exact split is unknown on Adreno.gpu_light_cullingis also 12.84 ms on Adreno vs ~1.0 ms on Mali, so the tiled-light path needs a net-benefit check there.Next measurements
temporal_history: false: isolates the accumulate/reprojection cost.max_distance: 10/15/20/30atVolumetricQuality::Low: shows how much of the cost is froxel depth resolution.Custom { grid_x: 128, grid_y: 80, grid_z: 64, composite_steps: 32 }, to separate grid size from light/shadow evaluation.If the results are still ambiguous, add sub-timestamps for volumetric inject, accumulate, and composite and expose them in the CSV/debug UI.
Acceptance criteria
Tablet volumetric/culling batch completed on
b7086621(Adreno 810, 2560x1600, 17 lights):gpu_volumetricsgpu_light_cullingOrder of levers: froxel grid/depth ≫ per-light inject loop > temporal history > shadowing. The 192-slice low-quality grid is the largest single cost; custom 128×80×64 saves 125 ms. Tiled culling is net-positive on Adreno, and tile 8 is better than 16/32 there.
Added volumetric sub-timestamps on
feat/perf-timingsin7060c5bf:Next: capture those three columns on the tablet, then choose a mobile volumetric grid/depth tier and evaluate
TILE_SIZE = 8as a default. No defaults were changed in this batch.Implemented the first mobile tier and Adreno-friendly tile size on
feat/perf-timings:3233c0b5 perf(renderer): add mobile volumetric tier and 8px light tilesVolumetricQuality::Mobile: X/Y gridresolution / 20, fixed 64 depth slices, 32 composite steps. At 2560x1600 this is 128x80x64, matching the best measured custom variant.TILE_SIZEis now 8. Tablet measurement was 7.06 ms culling / 32.53 ms scene versus 13.08 / 38.40 at 16; Mali was neutral-to-positive.The test project’s copied
AllInOne/src/lib.rsmust be synced to the updatedExamples/all-in-one/src/lib.rsfor the Android Mobile tier to take effect. Otherwise it will still use Low.Expected next capture:
After that capture, remaining tablet costs should be re-split with the new volumetric sub-timestamps. Composite (~26 ms) and per-light inject are likely the next candidates; history can follow.
Mobile tier
3233c0b5verified on both devices:gpu_volumetricsgpu_light_cullinggpu_scene_total*Mali inject timestamps remain ~0.02 ms; the aggregate and other stages are reliable.
Composite is now 61% of tablet volumetrics and ~93% of phone volumetrics.
de1d9883reduces the Mobile composite from 32 to 16 integration steps; the 128x80x64 grid and 64 depth slices are unchanged. Next capture should show composite near half its current cost; check for banding at the 16-step setting.The 8 px tiles also produced a larger Mali win than expected: deferred 21.13 → 7.44 ms and phone FPS 19.94 → 30.41.
16-step Mobile composite verified on both devices at
de1d9883:gpu_volumetricsgpu_volumetric_compositeNo visible fog banding in the captured views; 16 steps is acceptable for the current scene. Tablet is now 12.88 FPS / 77.65 ms against a 16.8 FPS / 59.3 ms non-volumetric floor.
The remaining tablet volumetric cost is inject ~11.1 ms, composite ~10.4 ms, accumulate ~2.5 ms. Composite is no longer the 21 ms bottleneck. This closes the Adreno volumetric tier issue; further inject work is optional and has diminishing headroom against the non-volumetric floor.