@@ -24,29 +24,57 @@ see [Lorenz Compiler performance benchmark][a].
...
@@ -24,29 +24,57 @@ see [Lorenz Compiler performance benchmark][a].
## 2. Use BLAS Library
## 2. Use BLAS Library
It is important to use the BLAS library that performs well on AMD processors.
It is important to use the BLAS library that performs well on AMD processors.
We have measured the best performance with the MKL;
To combine the optimizations for the general CPU code and have the most efficient BLAS routines we recommend the combination of lastest Intel Compiler suite, with Cray's Scientific Library bundle (LIBSCI). When using the Intel Compiler suite includes also support for efficient MPI implementation utilizing Intel MPI library over the Infiniband interconnect.
however, the MKL BLAS must be ‘tricked’ to believe it is working with an Intel CPU.
For the compilation as well for the runtime of compiled code use:
This example runs the BINARY.x, placed in ${HOME} as 2 MPI processes, each using 64 cores of a single socket of a single node.
Another example would be to run a job on 2 full nodes, utilizing 128 cores on each (so 256 cores in total) and letting the LIBSCI efficiently placing the BLAS routines across the allocated CPU sockets:
This assumes you have allocated 2 full nodes on Karolina using SLURM's directives, e. g. in a submission script:
```code
#SBATCH --nodes 2
#SBATCH --ntasks-per-node 128
```
!!! note
**Don't forget** before the run to ensure you have the correct modules and loaded and that you have set up the LD_LIBRARY_PATH environment variable set as shown above (e.g. part of your submission script for SLURM).
Most MPI libraries do the binding automatically. The binding of MPI ranks can be inspected for any MPI by running `$ mpirun -n num_of_ranks numactl --show`. However, if the ranks spawn threads, binding of these threads should be done via the environment variables described above.
The choice of BLAS library and its performance may be verified with our benchmark,
!!! note
see [Lorenz BLAS performance benchmark][a].
Most MPI libraries do the binding automatically. The binding of MPI ranks can be inspected for any MPI by running `$ mpirun -n num_of_ranks numactl --show`. However, if the ranks spawn threads, binding of these threads should be done via the environment variables described above.