perf(renderer): 16 point/spot lights cost ~29 ms/frame; verify tiled light culling #1087
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#1087
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 16 point/spot lights cost about 29.1 ms/frame on the Mali-G720 phone. With shadows already disabled, removing all point/spot lights reduced
gpu_deferredfrom 33.15 ms to 4.01 ms andgpu_scene_totalfrom 36.25 ms to 7.00 ms.The forward path has the same issue and is only ~8.7% faster overall than deferred; it evaluates all lights per fragment without the tile list.
Hypotheses
tile_aabbuses the min/max depth of a 16x16 tile and builds the world-space AABB of that depth slice. At far depth this can span most of the scene, so many tiles include lights that do not actually affect the tile.Next measurements
tile_light_countsand report average/max lights per tile, plus the overflow count.Do not implement automatic resolution/refresh changes; #1083 remains separate.
Acceptance criteria
Batch results: forcing the full 17-light loop is 71.27 ms vs 73.83 ms for tiled culling, and tile sizes 8/16/32 are indistinguishable. The tile lists are effectively all-inclusive.
The reason is #1088: point/spot “range” is
intensity / 0.01; intensities 30–60 yield radii of ~55–77 world units, covering the whole scene. Fixing the light range should make this culling test meaningful. Re-run E/F after #1088 before redesigning the culling bounds.