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
Last revisionBoth sides next revision
doku:perf-report [2015/09/15 09:55] shdoku:perf-report [2020/09/24 13:14] sh
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: ==== ==== Usage: ====
Line 13: Line 13:
    #SBATCH -J prflng            #SBATCH -J prflng        
    #SBATCH -N 2     #SBATCH -N 2 
-   #SBATCH --time=00:10:00+   #SBATCH -L allinea@vsc 
 +   #SBATCH --ntasks-per-node=16 
 +   #SBATCH --ntasks-per-core=1
      
    module purge    module purge
-   module load intel-mpi/+   module load intel/18 intel-mpi/2018 allinea/20.1_FORGE
-   module load allinea/5.10+
          
-   perf-report mpirun -np 32 a.out+   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 !
  
-This produces .edf and .trc files. Then one has to  +==== Further Reading: ==== 
-merge these files via: +''/opt/sw/x86_64/glibc-2.17/ivybridge-ep/allinea/20.1_FORGE/doc/userguide-forge.pdf'' ( part 4, explanations, examples, typical cases  )
-<code> +
-tau_merge -e events.*.edf -m vasp_events.edf tautrace.*.0.0.trc vasp.trc +
-</code> +
-and finally the 'vasp.trc' and 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.slog2) can 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.txt
  • Last modified: 2022/11/04 10:12
  • by goldenberg