Earlier quoted context omitted.
I can't reply to the person that replied to you, so > You’re looking as a dev, but the reality is that a consumer cannot see technical debt. The consumer can't _see_ technical debt, but they sure as heck can be impacted by it. - Technical debt means the code base is harder to work with later. So fixes/enhancements take longer to make it into the code (and sometimes never can) - This particular type of technical debt…
>the next developer may us it as an example These hacks are game specific, so another developer wouldn't get them.
FP8 is ~100 tflops faster when the kernel name has "cutlass" in it
91–100 of 114 posts
Re: FP8 is ~100 tflops faster when the kernel name has "cutlass" in it
#92Earlier quoted context omitted.
> As a gamer, this seems fine to me As a software developer, it almost certainly has a bad effect on the ecosystem long term. "Hacks shit in" is the very definition of technical debt, and that has a cost that someone, somewhere is going to have to pay in some form.
You’re looking as a dev, but the reality is that a consumer cannot see technical debt. If the studio churns out a game, the vendor sprinkles on some optimizations, people play it and move on, then the tech debt just vaporizes into the void. It’s not real at that point.
Re: FP8 is ~100 tflops faster when the kernel name has "cutlass" in it
#93Earlier quoted context omitted.
Was it a scandal at the time? My understanding of how per-game card-driver optimizations work today is: 1. AAAA Game Studio shits out another unoptimized clunker 2. nvidia considers it a reputational risk if games run at 30 FPS on a 5090 3. They go in, look at the perverse ways the game misuses rendering primitives, and then hacks shit in to make whatever bad things they're doing less bad. As a gamer, this seems fine…
I was surprised to see “AAAA”. I didn’t know there were 4 As now. “AAAA Game Studio shits out another unoptimized clunker” seems a paradoxical statement to me. I would have thought “AAAA” meant “highly resourced” game company. Does it just mean high revenue? Lots of players?
Re: FP8 is ~100 tflops faster when the kernel name has "cutlass" in it
#94Earlier quoted context omitted.
Was it a scandal at the time? My understanding of how per-game card-driver optimizations work today is: 1. AAAA Game Studio shits out another unoptimized clunker 2. nvidia considers it a reputational risk if games run at 30 FPS on a 5090 3. They go in, look at the perverse ways the game misuses rendering primitives, and then hacks shit in to make whatever bad things they're doing less bad. As a gamer, this seems fine…
I was surprised to see “AAAA”. I didn’t know there were 4 As now. “AAAA Game Studio shits out another unoptimized clunker” seems a paradoxical statement to me. I would have thought “AAAA” meant “highly resourced” game company. Does it just mean high revenue? Lots of players?
Re: FP8 is ~100 tflops faster when the kernel name has "cutlass" in it
#95Earlier quoted context omitted.
Was it a scandal at the time? My understanding of how per-game card-driver optimizations work today is: 1. AAAA Game Studio shits out another unoptimized clunker 2. nvidia considers it a reputational risk if games run at 30 FPS on a 5090 3. They go in, look at the perverse ways the game misuses rendering primitives, and then hacks shit in to make whatever bad things they're doing less bad. As a gamer, this seems fine…
> As a gamer, this seems fine to me As a software developer, it almost certainly has a bad effect on the ecosystem long term. "Hacks shit in" is the very definition of technical debt, and that has a cost that someone, somewhere is going to have to pay in some form.
Re: FP8 is ~100 tflops faster when the kernel name has "cutlass" in it
#96Earlier quoted context omitted.
It's like 5-10% here
Correct, this is the actual headline too. 100 tflops sure seems like it'd be more than that, but here we are. If the headline was "FB8 is ~7% faster when kernel name has 'cutlass' in it...", it wouldn't seem sensational.
Re: FP8 is ~100 tflops faster when the kernel name has "cutlass" in it
#97Earlier quoted context omitted.
I think you're the one doing that to the tweet, actually.
What are you talking about? When I view the tweet, the only text I see is: > > fp8 is 100 tflops faster when the kernel name has "cutlass" in it > kms
Re: FP8 is ~100 tflops faster when the kernel name has "cutlass" in it
#98Earlier quoted context omitted.
What are you talking about? When I view the tweet, the only text I see is: > > fp8 is 100 tflops faster when the kernel name has "cutlass" in it > kms
And it includes a link to show that this is the context it came from.
In order to get to the part that you're trying to hold me accountable for, I would furthermore have to click onto the commits tab and search through a 93-commit PR.
I thought today I was using a site where trying to think the best of people and propose that someone had taken something out of context, based on the immediately available context having a simpler explanation, would not get me treated like a corporate shill (for a company I don't even care about). Apparently I was wrong.
Re: FP8 is ~100 tflops faster when the kernel name has "cutlass" in it
#99And what’s the downside of using that kernel name? It can’t just be that it’s faster and nothing else. Unless they included lots of sleep(x) calls.
There might be optimizations that are only safe for the code that this was an intender for.
Re: FP8 is ~100 tflops faster when the kernel name has "cutlass" in it
#100Earlier quoted context omitted.
Was it a scandal at the time? My understanding of how per-game card-driver optimizations work today is: 1. AAAA Game Studio shits out another unoptimized clunker 2. nvidia considers it a reputational risk if games run at 30 FPS on a 5090 3. They go in, look at the perverse ways the game misuses rendering primitives, and then hacks shit in to make whatever bad things they're doing less bad. As a gamer, this seems fine…
> As a gamer, this seems fine to me As a software developer, it almost certainly has a bad effect on the ecosystem long term. "Hacks shit in" is the very definition of technical debt, and that has a cost that someone, somewhere is going to have to pay in some form.
There is no reason anyone has to pay each and every iota of technical debt. Plenty of things with technical debt hit end of life and no one ever looks in that code again. I suspect most technical debt goes this way - in program, program never updates (or minor updates), then dies.
Your claim would require every piece of technical debt in anything ever (code, buildings, cars, anywhere) has to be removed before the thing goes end of life or goes into a mode where it never is changed. That seems ludicrous to me.