- 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 -
Vampirtrace: Difference between revisions
(Added software info box) |
|||
| Line 1: | Line 1: | ||
The VampirTrace 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 relink the program with the VampirTrace library. A new compilation of the program source code is only necessary if program-specific events should be added. | {{Infobox software | ||
| description = The VampirTrace 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 relink the program with the VampirTrace library. A new compilation of the program source code is only necessary if program-specific events should be added. | |||
| developer = ZIH TU Dresden and JSC/FZ Juelich | |||
| available on = [[NEC Nehalem Cluster]] | |||
| category = [[:Category:Performance Analyzer|Performance Analyzer]] | |||
| license = BSD License | |||
| website = [http://tu-dresden.de/die_tu_dresden/zentrale_einrichtungen/zih/forschung/software_werkzeuge_zur_unterstuetzung_von_programmierung_und_optimierung/vampirtrace/index_html/document_view?cl=enhttp://gcc.gnu.org/ VampirTrace homepage] | |||
}} | |||
== Introduction == | == Introduction == | ||
Tracing with Vampir in three steps: | Tracing an application with Vampir is done in three steps: | ||
# Compiling with the vampirtrace wrappercompiler | # Compiling with the vampirtrace wrappercompiler | ||
Revision as of 21:57, 2 March 2010
| The VampirTrace 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 relink the program with the VampirTrace library. A new compilation of the program source code is only necessary if program-specific events should be added. |
| ||||||||||||
Introduction
Tracing an application with Vampir is done in three steps:
- Compiling with the vampirtrace wrappercompiler
- Running the application
- Analysing the trace files using vampir or vampir-server
For detailed usage of Vampirtrace see the user manual which can either be found on your local machine or in the internet.
Usage
Compiling with the vampirtrace wrappercompiler
First load the needed software module:
Now you can compile your application using the wrapper compilers vtcc, vtc++ or vtf90 as described in the user VampirTrace manual.
vtf90 -vt:f90 mpif90 vtcc -vt:cc mpicc
Generating the trace files
Run your applicatin as usual. This will generate the needed tracefiles
BW-Grid special:
On the BW-Grid you first have to login to a node as some libs are not accessible from the frontend
Viewing traces with vampir or Vampir-Server
There are two GUIs available to view your trace files: Vampir and Vampir-Server. For both you will need read access to all generated output files (*.def.z, *.events.z, *.otf).
Vampir
Vampir is the sequential version of the graphical trace file analyzing software. It is capable of analyzing smaller trace files and should not be used for files which have 100MB or more.
Vampir-Server
Vampir-Server is the parallel version of the graphical trace file analyzing software. It can be found on the SX-8 frontend (a1.hww.de). The tool consists of a client and a server. The server itself is a parallel MPI Program.
First load the necessary software module
Now start the server and afterwards the client
Remember the port number which will be displays as you will need it later on. Then start the graphical client
The last step is to connect the client to the server using the port number offered you from the server. This is done under
file <math>\rightarrow</math> Connect to Server ...
Then you can open your traces via
file <math>\rightarrow</math> Open Tracefile ...
Select the desired *.otf file
Trouble shooting
If the program crashes unexpectedly it is possible that there is not enough space on the node local /tmp. A solution is to use a workspace in combination with the VT_PROFM_LDIR variable
In some cases problems concerning library issues occure. In this case it could help