The same way one should always do so on an advanced out-of-order CPU largely being programmed in modern high level languages: through thorough profiling and performance testing.
You can only see the performance values for yourself, or believe the SPEC benchmarks.
If you're working in an HPC center, you may ask your fellow centers and get off-the-record answers, sometimes.
https://www.intel.com/content/www/us/en/products/docs/proces...
I remember reading the datasheets myself and not being able to find it, together with my teammates.
So they changed their mind two months ago, and shared this info for their processors.
Guess that the information lost its significance.
Either way, a processor significantly throttles under AVX-512 load. Nice.
Edit: I re-read the document and found our SKUs under the "newly added" table and, clarified the comment.
Original Datasheets:
- https://www.intel.com/content/www/tr/tr/products/docs/proces...
- https://www.intel.com/content/www/tr/tr/products/docs/proces...
Spec Update - For re-referencing:
- https://www.intel.com/content/dam/www/public/us/en/documents...
Our mostly used SKUs are released in 2019 so, its data was not available since years ago. Intel was very open about how their tech worked when it was new, needed to show their tech against the competition and not limited by thermal constraints.
When they became the dominant player, they didn't feel bad about hiding small but important details from their consumers.
Until EPYC came and pushed & prodded them around, they didn't bother to release both "R" processors and the related frequency scaling data for AVX-512 loads.
https://lemire.me/blog/2018/08/25/avx-512-throttling-heavy-i...
https://lemire.me/blog/2018/08/24/trying-harder-to-make-avx-...
https://lemire.me/blog/2018/08/15/the-dangers-of-avx-512-thr...
Any performance gain from fewer cycle cost may be lost from the CPU being slower. Maybe there are situations where AVX-512 is faster but how is one to reason about performance when some instructions can slow the CPU.