- 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
m (Fixed path) |
(Link Paraver and Dimemas) |
||
| (7 intermediate revisions by 3 users not shown) | |||
| Line 1: | Line 1: | ||
<b> Note, this page is outdated </b> | |||
{{Infobox software | {{Infobox software | ||
| description = 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. | | description = The Extrae library allows MPI communication events of a parallel program to be recorded as a trace file that can be analysed, e.g., visually with [[Paraver]] or used as an input for a simulator as [https://tools.bsc.es/dimemas Dimemas]. Additionally, certain program-specific events can also be included. To record MPI communication events, simply run the program with the Extrae library preloaded. | ||
| developer = BSC | | developer = BSC | ||
| available on = [[ | | available on = [[Hazel Hen]], [[Vulcan]] | ||
| category = [[:Category:Performance Analyzer|Performance Analyzer]] | | category = [[:Category:Performance Analyzer|Performance Analyzer]] | ||
| license = GPL | | license = GPL | ||
| website = [ | | website = [https://tools.bsc.es/extrae Extrae homepage] | ||
}} | }} | ||
<b> Note, this page is outdated </b> | |||
== Introduction == | == Introduction == | ||
| Line 21: | Line 25: | ||
Now set up the environment for the run. | Now set up the environment for the run. | ||
{{Command| command = | {{Command| command =<div>export LD_PRELOAD=$HLRS_EXTRAE_ROOT/lib/libmpitrace.so <br> | ||
export LD_PRELOAD=$ | export EXTRAE_CONFIG_FILE=extrae.xml</div> | ||
export EXTRAE_CONFIG_FILE=extrae.xml | |||
}} | }} | ||
Finally run your application as usual. This will generate the needed tracefiles. | Finally run your application as usual. This will generate the needed tracefiles. | ||
| Line 42: | Line 45: | ||
== External Links == | == External Links == | ||
* [http://www.bsc.es/plantillaF.php?cat_id=52 Extrae Homepage] | * [http://www.bsc.es/plantillaF.php?cat_id=52 Extrae Homepage] | ||
[[Category:Performance Analyzer]] | |||
Latest revision as of 08:17, 22 September 2023
Note, this page is outdated
| The Extrae library allows MPI communication events of a parallel program to be recorded as a trace file that can be analysed, e.g., visually with Paraver or used as an input for a simulator as Dimemas. 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