... | ... | @@ -2,9 +2,26 @@ |
|
|
### Why
|
|
|
We want to know if our MPI profile makes sense
|
|
|
|
|
|
### Sources
|
|
|
### Where
|
|
|
This has been tested on [licallo](https://crimson/oca.eu)
|
|
|
|
|
|
### Inspiration
|
|
|
We will use Intel tools to do so, this work is based on their [tutorial](https://software.intel.com/en-us/itac-vtune-mpi-openmp-tutorial-lin)
|
|
|
|
|
|
### The big picture
|
|
|
To get a first impression on how are things, we use [performance_snapshots](https://software.intel.com/en-us/itac-vtune-mpi-openmp-tutorial-lin-get-a-performance-overview-with-application-performance-snapshot) and need to load the matching module:
|
|
|
```
|
|
|
$ module load performance_snapshots/2019.4
|
|
|
$ which aps
|
|
|
/trinity/shared/apps/170135/x86_64/intel-2019/vtune_amplifier_2019.4.0.597835/bin64/aps
|
|
|
```
|
|
|
Then:
|
|
|
1. we do a test run to collect data, this is achieved by prefixing the executable with the **aps** command. Here is a [script example]($13).
|
|
|
2. we
|
|
|
```$ aps-report aps_result_20190809 -O report.html > report.txt
|
|
|
```$
|
|
|
`report.txt` will contain a text version of the report, `report.html` the hml version.
|
|
|
|
|
|
### Config files
|
|
|
* For a test based on *3D_stellar_radiation_disk*, you can use [this file]($12)
|
|
|
|
... | ... | |