Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
doku:perf-report [2015/09/15 09:36]
sh
doku:perf-report [2022/11/04 10:12] (current)
goldenberg [Usage:]
Line 1: Line 1:
-===== VSC-3: Performance Report (Allinea) =====+===== Performance Reports =====
    
  
 ==== Synopsis: ====  ==== Synopsis: ==== 
-''perf-report'' is a lightweight profiling tool that provides basic information about where the computing time is actually spent in a given application. It is developed by Allinea [[http://www.allinea.com/products/allinea-performance-reports]] and very simple to use, i.e. by simply inserting the call to ''perf-report'' prior to the usual execution of the program+''perf-report'' is a lightweight profiling tool that provides basic information about where the computing time is actually spent in a given application. It is developed by ARM (formerly Allinea[[https://developer.arm.com/tools-and-software/server-and-hpc/debug-and-profile/arm-forge]] and very easy to use, i.e. by simply prefixing the usual executable with a call to ''perf-report''
 +It is nowadays integral part of [[doku:forge|ARM's forge]].
  
 +==== Usage: ====
 +For example, analyzing a simple MPI job could be done with the help of the following submit script to [[doku:slurm|SLURM]]
  
 +   #!/bin/bash
 +   #
 +   #SBATCH -J prflng        
 +   #SBATCH -N 2 
 +   #SBATCH --ntasks-per-node=16
 +   #SBATCH --ntasks-per-core=1
 +  
 +   module purge
 +   module load openmpi/4.1.4-gcc-12.2.0-x6sxxj3 arm/20.1_FORGE
 +    
 +   perf-report srun --jobid $SLURM_JOB_ID --mpi=pmi2 -n 32 ./a.out
 +   
 +This will result in the creation of two summary files in *.txt and *.html format providing an overview of the relative time spent in MPI, I/O, OpenMP etc. Note the 'Energy' section in recent releases !
  
-==== VAMPIRTRACE ==== +==== Further Reading: ==== 
- +''/opt/sw/x86_64/glibc-2.17/ivybridge-ep/allinea/20.1_FORGE/doc/userguide-forge.pdf''part 4, explanations, examples, typical cases  )
-VAMPIRTRACE is maintained by the computing centre of TU Dresden. Linking the Libraries to your executable Produces profiling and tracing information. Currently it is available for free. +
- +
-[[http://tu-dresden.de/die_tu_dresden/zentrale_einrichtungen/zih/forschung/software_werkzeuge_zur_unterstuetzung_von_programmierung_und_optimierung/vampirtrace|VAMPIRTRACE Homepage]] +
- +
-Location on VSC-1: ''/opt/vampirtrace'' +
- +
-==== TAU ==== +
- +
-Another Tool is TAU, which is provided by different Institutions [[http://www.cs.uoregon.edu/research/tau/docs.php|TAU Homepage]] +
-It provides viewing tools for profiles and traces (PARAPROF and JUMPSHOT) +
- +
-Location on VSC-1: ''/opt/tau'' +
- +
-Sample jobscript for generating tracing information using TAU +
- +
-   #$ -N tau +
-   #$ -q all.+
-   #$ -pe mpich 8 +
-   #$ -l h_rt=2:0:+
-   mpirun  -m $TMPDIR/machines -np $NSLOTS tau_exec -T PROFILE -T TRACE -io ./vasp'' +
- +
-This produces .edf and .trc files. Then one has to  +
-merge these files via: +
-<code> +
-tau_merge -e events.*.edf -m vasp_events.edf tautrace.*.0.0.trc vasp.trc +
-</code> +
-and finally the 'vasp.trcand the 'vasp_events.edf' files need to  +
-be converted into .slog2 format: +
-<code> +
-tau2slog2 vasp.trc vasp_events.edf -o vasp.slog2 +
-</code> +
-This file (vasp.slog2can be visualized with jumpshot. +
- +
- +
-===== Visualization of Profiles and Traces ===== +
- +
- +
- +
-==== VAMPIR ==== +
-Currently a demo version of [[http://www.vampir.eu|VAMPIR]] is installed on VSC-1. It can visualize VAMPIRTRACE files, as well as other formats such as OTF +
- +
-Location on VSC-1: ''/opt/vampir'' +
- +
-==== JUMPSHOT and PARAPROF ==== +
- +
-Both are installed together with TAU. +
- +
-[[http://www.mcs.anl.gov/research/projects/perfvis/software/viewers/index.htm|JUMPSHOT Homepage]] +
- +
  • doku/perf-report.1442309761.txt.gz
  • Last modified: 2015/09/15 09:36
  • by sh