Deferred lighting default per GPU class (split vs uber) #824
Labels
No labels
amd
avatars
bug
builder
cannot-reproduce
crash
epic
feature
from-viewer
gl-removal
known-limitation
monitoring
parity
perf
platform
priority
critical
priority
high
priority
low
priority
medium
provenance
rendering
rt
status
in-progress
status
testing
status
up-next
triage
ui
upstream
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
sky_line/Slipstream#824
Loading…
Add table
Add a link
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?
On a GTX 1080 the uber kernel beats the split at both Firestorm-equivalent (-0.7 ms) and high settings (-2.0 ms): the split's combine runs at the same 126 registers as uber and the extra passes re-decode the G-buffer. The split was tuned on an RTX 5090. Revisit after the froxel grid and register work (both paths should get much lighter), then pick per GPU class; blocked on #809 for any live switch.
Context: measured on a GTX 1080 (Pascal) at 4K with the test-control channel and the shader clock (RenderVKShaderClockLighting) / pipeline stats (RenderVKPipelineStats). The frame is GPU-bound but not bandwidth-bound (memory controller ~36% busy on the 1080, ~14% on a 5090): it is latency / occupancy bound, so trading a little memory traffic for fewer registers and fewer dependent loads should help every GPU generation.
Fixed in 1.5.0 Beta 1 (
4d6bb1f64b). Reopen if you still see it.