> Indeed, but the problem is that often AVX intensive code triggers intel to significantly throttle Xeon-W, HEDT, and consumer processors suffer this to a much

> Indeed, but the problem is that often AVX intensive code triggers intel to significantly throttle Xeon-W, HEDT, and consumer processors suffer this to a much smaller extent than Skylake-SP does, and this slowdown is already baked into the benchmarks (the deviation from benchmarks only really exists for mixed workloads). In most cases, AVX is still a huge speedup. Also, on consumer+HEDT you can manually configure the AVX offset anyway. Want zero offset, and can handle the power/heat? Go hog wild... > Most notably even on the most FP intensive code don't seem to benefit much from the higher end xeons (with two AVX512 units) over the lower models with a single AVX512 unit. Intel's documentation on some of the HEDT chips was incorrect, the i7s actually have dual AVX512 as well as the i9s. If you were referring to HEDT as "Xeons" that would be why. Otherwise, it might be another documentation issue. The difference should be very clear in something like x265 encoding.