> but as opposed to the old intel avx512 cores that got endless (deserved?) bad press for their transition behavior, this is more or less seamless.
The problem with Intel was, the AVX frequencies were secrets. They were never disclosed in later cores where power envelope got tight, and using AVX-512 killed performance throughout the core. This meant that if there was a core using AVX-512, any other cores in the same socket throttled down due to thermal load and power cap on the core. This led to every process on the same socket to suffer. Which is a big no-no for cloud or HPC workloads where nodes are shared by many users.
Secrecy and downplaying of this effect made Intel's AVX-512 frequency and behavior infamous.
Oh, doing your own benchmarks on your own hardware which you paid for and releasing the results to the public was verboten, btw.
The problem with Intel was, the AVX frequencies were secrets. They were never disclosed in later cores where power envelope got tight, and using AVX-512 killed performance throughout the core. This meant that if there was a core using AVX-512, any other cores in the same socket throttled down due to thermal load and power cap on the core. This led to every process on the same socket to suffer. Which is a big no-no for cloud or HPC workloads where nodes are shared by many users.
Secrecy and downplaying of this effect made Intel's AVX-512 frequency and behavior infamous.
Oh, doing your own benchmarks on your own hardware which you paid for and releasing the results to the public was verboten, btw.