... | ... | @@ -284,7 +284,7 @@ Use "module keyword key1 key2 ..." to search for all possible modules matching a |
|
|
- load a module
|
|
|
|
|
|
```
|
|
|
module load mpi/openmpi/4.0.2/gcc-8.2.1
|
|
|
module load library/mpi/openmpi/4.0.2/gcc-8.3.1
|
|
|
```
|
|
|
|
|
|
- show loaded modules
|
... | ... | @@ -292,12 +292,12 @@ module load mpi/openmpi/4.0.2/gcc-8.2.1 |
|
|
module li
|
|
|
|
|
|
Currently Loaded Modules:
|
|
|
1) mpi/openmpi/4.0.2/gcc-8.2.1
|
|
|
1) library/mpi/openmpi/4.0.2/gcc-8.3.1
|
|
|
```
|
|
|
|
|
|
- delete one module
|
|
|
```
|
|
|
module del mpi/openmpi/4.0.2/gcc-8.2.1
|
|
|
module del library/mpi/openmpi/4.0.2/gcc-8.3.1
|
|
|
```
|
|
|
|
|
|
- purge all modules
|
... | ... | @@ -348,7 +348,7 @@ compilation terminated. |
|
|
So we need to load the correct module and use the correct compiler
|
|
|
|
|
|
```
|
|
|
$ module add mpi/openmpi/4.0.2/gcc-8.2.1
|
|
|
$ module add library/mpi/openmpi/4.0.2/gcc-8.3.1
|
|
|
```
|
|
|
|
|
|
- mpicc hello.c -o hello
|
... | ... | @@ -367,7 +367,7 @@ Hello world from process 000 out of 001, processor name res-hpc-lo01.researchlum |
|
|
|
|
|
Here you can see that we ran the program only on 1 core of the cpu. (which is the same as running: mpirun -np 1 ./hello) (np = number of processes to launch)
|
|
|
|
|
|
To make use of the MPI capabilities of the program, we have to run the program with the "mpirun" which comes with the loaded module mpi/openmpi/4.0.2/gcc-8.2.1
|
|
|
To make use of the MPI capabilities of the program, we have to run the program with the "mpirun" which comes with the loaded module library/mpi/openmpi/4.0.2/gcc-8.3.1
|
|
|
|
|
|
- mpirun ./hello
|
|
|
|
... | ... | @@ -732,7 +732,7 @@ Node-Core reservation: |
|
|
|
|
|
```
|
|
|
module purge
|
|
|
module add mpi/openmpi/4.0.2/gcc-8.2.1
|
|
|
module add library/mpi/openmpi/4.0.2/gcc-8.3.1
|
|
|
|
|
|
git clone https://github.com/intel/mpi-benchmarks
|
|
|
cd mpi-benchmarks
|
... | ... | |