3 ms·
Numpy is something you could expect to find running on a workstation and Intel's workstation CPU line has had AVX-512 continuously since 2017.
by jeffbee 4y ago
Numpy is something you could expect to find running on a workstation and Intel's workstation CPU line has had AVX-512 continuously since 2017.
- mumumu 4y agoAlder Lake and Raptor Lake workstation (W680 Chipset) doesn't have AVX512 enabled.
- jeffbee 4y agoFair. The "entry workstation" thing from Intel is baffling. I was thinking Xeon W, but then of course there was the Xeon W-12xx that lacked AVX-512. In short, I was wrong. It would have been more correct to say that Intel has offered a workstation part with AVX-512 continuously since Skylake.
- bXVsbGVy 4y agoIntel released a couple days ago new Xeon-W CPUs with AVX-512. The wx-24xx uses the same p-cores as alder lake, but with avx-521 enabled. Same for wx-34xx but with raptor lake's p-core. The entry levels xeon are believed to be identical to Core ix, with the e-cores disabled and avx-512 enabled. The extra I/O and ECC support is done by the chipset. In summary, they just went to support avx-512 only on xeon w. This makes sense, since must be hard to schedule between cores with and w/o avx (the e-cores doesn't have avx).
- sliken 4y agoSad, big win for the Ryzen or future Zen 4 threadripper.
- cbsmith 4y agoThere 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.”