4 ms·
There was a longstanding issue where AVX-512 would trigger frequency throttling on a number of Intel CPUs, resulting in a net performance penalty for mixed work
by cbsmith 4y ago
There was a longstanding issue where AVX-512 would trigger frequency throttling on a number of Intel CPUs, resulting in a net performance penalty for mixed workloads.
- saagarjha 4y agoOk, but that hasn’t been a problem in a while.
- Rimintil 4y agoHasn't been a problem because software corrected for that, or hasn't been a problem because Intel resolved the underlying throttling issues with AVX-512?
- rurban 4y agoIt was only useful in a couple of corner cases, but not in general library functions. Intel could never fix its thermal issues, AMD did.
- mhh__ 4y agoBoth
- jackmott42 4y agoIt was never really a problem.
- cbsmith 4y agoYeah, but the mystique still lingers on.
- jackmott42 4y agoNo, there was a longstanding issue of people worrying that it would result in a net performance penalty for mixed workloads. Meanwhile people actually using AVX-512 dealt with that by making sure mixed workloads were batched appropriately and it is usually a big net win even if you don't worry about it.
- stephencanon 4y ago“Longstanding” here means “really only in a single CPU generation (SKX), and even then only if you were dumb and used like 50 AVX-512 instructions in isolation for no reason at all.”