Yautja93 t1_j6siuv1 wrote
Then should I use the browser version of it? Or it does the same?
_Xaradox_ t1_j6tq4yk wrote
Its a 200MHz reduction in memory clocks, highly unlikely you will notice any difference.
Edit: I don't know why I'm being downvoted, 200MHz on memory clocks is really not a significant difference. It's like 6800MHz instead of 7000MHz. We're talking, maybe, 1% performance loss.
Nevermind that it only seems to be affecting some 30-series cards.
It shouldn't happen, but since Nvidia were made aware, they published a fast temporary fix and a permanent fix is already on the way.
The-Protomolecule t1_j6u7959 wrote
It’s not the fact it’s insignificant, it’s the fact they’re causing an issue like this at all. Also 6800/7000 is a 2.9% loss of memory performance, because math.
That’s why you’re getting downvoted.
_Xaradox_ t1_j6w7ayy wrote
A 2.9% loss of memory clock does not directly equate to a 2.9% loss of performance.
The-Protomolecule t1_j7256br wrote
Of course not, but to say it’s 1% performance hit is just as much a random guess based on that guy being cool with voice software causing clock issues on GPUs, which it should NEVER do. If you’re running memory bandwidth constrained tasks it absolutely can be MORE than 2.9% if you’re starving the GPU.
Source: I build AI/ML training clusters for a living.
Tim_Allosaurus t1_j6ygbt2 wrote
Being downvoted for being reasonable and not hysterical.
Viewing a single comment thread. View all comments