You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using AMD GPU Analyzer we can now analyze our default shader code and see line-by-line resource usage including register pressure. As VGPR usage is one of the largest bottlenecks we have right now, it is something we should track and aim to reduce.
Right now the basic Godot scene fragment shader allocates 80 VGPRs and only uses 73. We should aim to reduce that number (or at least avoid needlessly increasing it).
Below are examples of the output you can get from AMD GPU analyzer which could be easily parsed to highlight changes and increases or decreases in register usage
Is there an automated way to use the Radeon GPU Analyzer on Linux from the command line (and ideally with a standard output format)? This would be required for it to be usable on the benchmarking server.
Is there an automated way to use the Radeon GPU Analyzer on Linux from the command line (and ideally with a standard output format)? This would be required for it to be usable on the benchmarking server.
I haven't used it from the command line but it looks like it can be used either from GUI or from the command line and it supports Ubuntu 20.04 https://gpuopen.com/rga/
Using AMD GPU Analyzer we can now analyze our default shader code and see line-by-line resource usage including register pressure. As VGPR usage is one of the largest bottlenecks we have right now, it is something we should track and aim to reduce.
Right now the basic Godot scene fragment shader allocates 80 VGPRs and only uses 73. We should aim to reduce that number (or at least avoid needlessly increasing it).
Below are examples of the output you can get from AMD GPU analyzer which could be easily parsed to highlight changes and increases or decreases in register usage
gfx1035_livereg_frag.txt
gfx1035_livereg_vert.txt
The text was updated successfully, but these errors were encountered: