We bought a single epyc node for testing, but we only reused our existing library (built on haswell with similar instruction set).
At the last EB user meeting I got recommended to use the undocumented MKL_DEBUG_CPU_TYPE with MKL in order to force it to use AVX2. As one might expect, the binaries build for haswell couldn't run, because intel "helpfully" puts a block that forces a cpu check before starting whenever you compile with -xHost. The VASP code, which we had only compiled with -xavx, ran fine. All the foss code I have tested seemed to run fine. We had a PhD student benchmark OpenFOAM for us, and using the same binaries (as compiled for Intel 2650v3), it ran ~ twice as fast on the 2x16 core EPYC node than on a 2x10 core 2650v3 node. Best regards, Mikael On Thu, Aug 16, 2018 at 2:38 PM Kenneth Hoste <[email protected]> wrote: > Dear EasyBuilders, > > Does anyone here have experience with using EasyBuild on AMD Epyc systems? > > Do the common toolchains (foss/2018a, intel/2018a or older) work out of > the box, or did you have to make some tweaks? > In particular, did the default of compiling with -xHost with the Intel > compilers work fine? > > In addition: any experiences on how the performance compares to recent > Intel systems for particular applications? > > > regards, > > Kenneth >
