Perf: Beta 10 slower than Beta 8 on RX 6700 XT (GPU-bound in pass 1; ray-traced sun likely on) #210
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#210
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?
A user reports lower FPS on Beta 10 than on Beta 8. The logs are attached (
logs.zip:Slipstream.log= Beta 10 / 0.12.0.36 with GPU timers and section timings;Slipstream.old= Beta 8 / 0.12.0.34, no timers).Hardware: AMD RX 6700 XT (RADV NAVI22, Vulkan 1.4.354, 12 GB), Ryzen 7 3700X, Linux.
First read of the logs
.old).log)Beta 10 is GPU-bound:
vk_acquireWait≈ 35 ms (the CPU waiting on the GPU).Ray-traced sun is probably on:
VKRTlines show the RT build (TLAS 63k instances, 13k static BLAS + 20 rigged groups) running every frame whileprojshadow=off(95 of 113 timer lines).projshadow=rt proj_n=62-64).To do
selectLitVariant) and texture residency (2930 vs 1562 MB is fine for 12 GB). Check TAA / upscaling and the new features on by default in Beta 9-10.OctreeErrorsinsertion warnings appear in both logs. That's pre-existing log spam, unrelated here, but worth its own look.Related: #185 (RT sun), #195 (RT sun optimization), #98 (low-end fixed costs).
Closing as stale: this Beta 10 vs Beta 8 comparison predates many performance changes (rigged LOD #561, shadow culling #564, geometry/VRAM work #573/#584, LL perf batches). If the RX 6700 XT is still slower on the current beta, please file a fresh report from Help > Report Bug and we'll compare against that.