4 ms·
Damn I wish we could simply buy a single socket AMD EPYC instead of a dual socket Intel Xeon. When compared at last gen Rome, scientific workloads compiled with
by reacharavindh 6y ago
Damn I wish we could simply buy a single socket AMD EPYC instead of a dual socket Intel Xeon. When compared at last gen Rome, scientific workloads compiled with Intel compiler that relied on AVX-512 a lot performed piss poor on AMD while other regular stuff flew ..
It is too hard to buy these awesome chips and have them NOT run the serious stuff that our group wants to. I wish AMD would come up with a solution that makes it magically work with code compiled for AVX-512 :-(
- gbrown_ 6y agoWhat's the workload if you don't mind me asking? Presumably the difference isn't just down to the smaller width of AVX2 but new instructions in the AVX-512 family?
- calaphos 6y agoRecompiling is not an option? Also seems weird that the binary only ships with a AVX512 codepath and not AVX2 as well. I remember there being also an issue of linked MKL libraries shipped with various software (e.g. Matlab) not using the appropriate AVX2 codepaths on 'unsupported' AMD processors and isn't was falling back on slow non vectorized code.
- brutos 6y agoIf you can recompile but the code was written to only target AVX-512 you can use https://github.com/simd-everywhere/simde https://github.com/simd-everywhere/simde to near effortlessly map the intrinsics to AVX2 (or lower).
- accountofme 6y agoI think the key issue here is the use of the intel compiler on a non intel product. Can you not recompile your code with GCC or LLVM? are the performance metrics that bad that they are not options? AMD has made the system... Engineer your solution if you want to use it :)
- gameswithgo 6y agocompile it for avx2 and you might still win