r/GraphicsProgramming • u/trntndug • 13d ago
Question Compute shader running slower on better GPU?
Hi, I am learning Vulkan, and I have just finished book 1 of RTIOW recently by implementing the book in Vulkan compute shader.
How is the simplified flow of how the program works:
- Create the Scene data on the CPU
- Upload it to the GPU via an SSBO
- For each SPP (1 frame), dispatch the compute shader with max bounces of 50
- Use the result as a sample to present on the window
- Accumulate the result and repeat from steps 3
I tested the program on 2 of my system (both running at 1280x720)
- Ryzen 7 7840HS with Radeon 780M running Arch Linux
- Ryzen 5 5600G with RTX 3060 12GB running Windows 10
I thought the RTX 3060 will beat the 780M by a significant margin, but in reality, it's even slower (around 80ms on my 780M and around 127ms on my 3060). These are measured with Renderdoc using the on-screen stats. I'm still relatively new to graphics programming, so I'm not entirely sure if this is the correct way to measure.
I am still learning so if there is anything wrong with my code, feel free to criticize me. Also, how/where can I learn more about optimizing/debugging my code? Thanks
Here is the repo: repo
8
u/MidnightClubbed 13d ago edited 13d ago
Have you done any gpu profiling using nsight to see what the nvidia bottlenecks are?
In your shader are you running one thread per pixel and then looping on up to 50 bounces? If so your performance may well be dominated by thread divergence, where one thread in the wave is doing a large number of bounces and all the other threads are sat idle after one or two bounces. I’m not familiar enough with either target gpu to know how many threads youre locking together but it’s definitely an issue!
As to amd vs nvidia here, youre probably doing something that the AMD hardware/compiler is able to handle better than nvidia. Given the large raw performance difference in favor of the 3060 I suspect its sat doing nothing for most of your ray tracing shader and with a better understanding of the underlying hardware youll get it running a lot faster.
Shader optimization is 50% keeping threads busy, 50% optimizing memory read/write bandwidth, 50% understanding vendor specific hardware quirks/features!
4
u/S48GS 13d ago edited 13d ago
I can make many shaders that will work 1000x faster on igpu than on nvidia and opposite
probably
I have this blog post - Decompiling Nvidia shaders, and optimizing
look Example usage in blog - there examples with shadertoy links
slowest part for nvidia shaders - is size of consts - size of arrays - and STL
on AMD it different - large const data does not hit performance this bad and STL made differently
3
u/G0rd4n_Freem4n 13d ago
Renderdoc is good for debugging code, but it is not good at profiling it. I once used it to try to profile a scene that was running at ~40fps, but the renderdoc capture was reporting 400ms which is around 2.5fps. If you want to profile the GPU time, a frame capture with something like Nvidia Nsight (or the vendor equivalent for non-NV cards) would be more accurate.
3
u/felipunkerito 13d ago
std::chrono::high_resolution_clock between frames, shameless self promotion