@TomF But Tom, don’t you like that fuzzy feeling you get when adding yet another permutation?
“Drop the amount of shaders you use from 10% to 5% with this one weird trick!”
@TomF That's a great article, though it's kinda sad that the most important thing in it isn't mentioned in the title and probably isn't noticed by most people:
Creating ways to visually profile the performance of your code is probably the #1 best way to know A) what needs to be optimized and B) whether or not what you did actually optimized it.
Hey, out there! You! Yes, you, the rendering engineer or technical artist! Add more visualization options to your shaders and code! Visual tuning FTW.
@TomF it’s… more complicated. Especially if you consider compute path instead of render.
This is another good post about IFs and branching by @BartWronski
@nemo @TomF @BartWronski I do love people explaining how ‘it’s more complicated than that’ TO THE MAN WHO WRITES THE ASSEMBLY LANGUAGE THAT SHADERS RUN ON.
Also Tom, don’t say you ‘discovered’ this post when you asked him to write in the first place because you didn’t want to:)
@jakesimpson @nemo @BartWronski As Jake points out, I am a GPU architect and one of my specialities is the bit that controls divergent branching :-)
Bart's post is also excellent. It's a very important point that:
-If you write an "if", the compiler can convert that to a select/step
-If you write a select/step, the compiler can't always convert it back to an "if"
Always be nice to your GPU compiler!
Jim
Tom Forsyth
Rubén Osorio
Oblomov
Felice
Giancarlo Todone
Jake Simpson
Bart Wronski 🇺🇦🇵🇸