- Infos im HLRS Wiki sind nicht rechtsverbindlich und ohne Gewähr -
- Information contained in the HLRS Wiki is not legally binding and HLRS is not responsible for any damages that might result from its use -
Extrae: Difference between revisions
From HLRS Platforms
Jump to navigationJump to search
No edit summary |
(→Usage) |
||
| Line 25: | Line 25: | ||
Now set up the environment for the run. | Now set up the environment for the run. | ||
{{Command| command =<div>export LD_PRELOAD=$ | {{Command| command =<div>export LD_PRELOAD=$HLRS_EXTRAE_ROOT/lib/libmpitrace.so <br> | ||
export EXTRAE_CONFIG_FILE=extrae.xml</div> | export EXTRAE_CONFIG_FILE=extrae.xml</div> | ||
}} | }} | ||
Revision as of 08:19, 23 May 2023
Note, this page is outdated
| The Extrae library allows MPI communication events of a parallel program to be recorded as a trace file. Additionally, certain program-specific events can also be included. To record MPI communication events, simply run the program with the Extrae library preloaded. |
| ||||||||||||
Note, this page is outdated
Introduction
Usage
First load the needed software module:
module load performance/extrae
Then create a configuration file for the extrae run. Commented templates can be found under $EXTRAE_HOME/share/example.
Now set up the environment for the run.
export LD_PRELOAD=$HLRS_EXTRAE_ROOT/lib/libmpitrace.so
export EXTRAE_CONFIG_FILE=extrae.xml
export EXTRAE_CONFIG_FILE=extrae.xml
Finally run your application as usual. This will generate the needed tracefiles.
Viewing traces with Paraver
To create a tracefile which is viewable with Paraver we have to convert the generated traces to a prv file
mpi2prv -f TRACE.mpits -o output.prv