4 ms·
I don't have exact performance numbers handy and haven't measured it personally but... from what I understand: * With heavy avx instructions churning, AVX shou
by trimbo 7y ago
I don't have exact performance numbers handy and haven't measured it personally but... from what I understand:
* With heavy avx instructions churning, AVX should still be a net positive performance-wise even when clocking down.
* It's when you're running AVX mixed with non-vector code that you can see the performance effects of clocking down, since you can drop way down from Turbo on non-vector instructions. Here are the different ranges [1]
[1] - Pages 14-21 https://www.intel.com/content/dam/www/public/us/en/documents/specification-updates/xeon-scalable-spec-update.pdf https://www.intel.com/content/dam/www/public/us/en/documents...
- robert_foss 7y agoFrom the Anandtech benchmark it was made clear that there is more than AVX-512 vs. clockspeed going on. Apparently AMD deemed implementing AVX-512 to be less desirable than spending the same silicon area on more cores. So there's both AVX-512 vs. clockspeed & AVX-512 vs. silicon budget going on. For many usecases having extra cores is a good trade-off.