Fp8 runs ~100 tflops faster when the kernel name has "cutlass" in it

Re:Fp8 runs ~100 tflops faster when the kernel name has "cut... by AnotherGoodName on Friday October 03, 2025 @11:13AM (#45463904)

Nvidia has a control panel with it's drivers. Open it up -> Manage 3D settings -> Program Settings. Scroll through and see how every single program/game you have installed openly has different defaults in it based on application name. As someone noted above others do the same thing.

Eg. Frostpunk has Antialiasing for transparency layers on. Slay the spire does not. I never set these settings. Nvidia literally does a lookup on first run for what they judge as best defaults and sets these appropriately.

Every single game/program you install has different options from a huge list of possible optimizations.

[ Parent | on HN ]

Re:Fp8 runs ~100 tflops faster when the kernel name has "cut... by umanwizard on Friday October 03, 2025 @12:12PM (#45464569)

Applying different standard settings is pretty different from "hijacking and modifying the rendering loop", though.

[ Parent | on HN ]

Re:Fp8 runs ~100 tflops faster when the kernel name has "cut... by altairprime on Friday October 03, 2025 @04:12PM (#45467262)

[delayed]

[ Parent | on HN ]

Re:Fp8 runs ~100 tflops faster when the kernel name has "cut... by umanwizard on Saturday October 04, 2025 @02:08PM (#45475339)

But the comment I replied to wasn’t talking about runtime patching or any of the other settings you mentioned. It was talking about changing GPU settings for specific programs. Not changing anything about the program itself.

[ Parent | on HN ]

Re:Fp8 runs ~100 tflops faster when the kernel name has "cut... by dahart on Friday October 03, 2025 @05:53PM (#45468247)

That’s not what @torginus was referring to. There’s nothing wrong with having and exposing application specific settings. There’s nothing wrong with drivers having application specific optimization patches either, but that’s a very different thing.

[ Parent | on HN ]