- Infos im HLRS Wiki sind nicht rechtsverbindlich und ohne Gewähr -

# Vampirtrace

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

## Introduction

Tracing with Vampir in three steps:

1. Compiling with the vampirtrace wrappercompiler
2. Running the application
3. 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 you should load the needed software module:

module load performance/vampirtrace


Now you should compile your application using the wrapper compilers vtcc, vtf90, ... as described in the user VampirTrace manual.

For MPI you will need at least to specify the name of your mpi compiler to vampirtrace

vtcc  -vt:cc  mpicc
vtf90 -vt:f90 mpif90


### 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

qsub -I -l walltime=1:00:00


### Viewing traces with vampir or Vampir-Server

Because Vampir and Vampir-Server are GUIs don't forget to use X-forwarding when you login via ssh. You will need read access to all generated output files (*.def.z, *.events.z, *.oft).

#### 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 we have to load the necessary software modules

module load vampir-server/1.10.0


Now start the server

vngd &


and remember the port number it displays. Then start the graphical client

vng


The last step is to connect the client to the server. This is done under

file $\rightarrow$ Connect to Server ...


Then you can open your traces via

file $\rightarrow$ Open Tracefile  ...


Select the ' *.oft ' 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

export LD_LIBRARY_PATH=/opt/NECcomp/compiler100/ia64/lib