Différences

Ci-dessous, les différences entre deux révisions de la page.

Lien vers cette vue comparative

Les deux révisions précédentes Révision précédente
Prochaine révision
Révision précédente
outils_analyse:tau [2015/02/27 13:37] – supprimée adminoutils_analyse:tau [2016/04/22 09:04] (Version actuelle) – admin
Ligne 1: Ligne 1:
 +====== TAU ======
 +TAU is an MPI program analyzer. It generates all necessary information during the program
 +execution, so that it can be read after it and displayed by a specialized program.
 +
 +
 +
 +===== Installed version =====
 +
 +  * 2.25 compiled with GCC and Open MPI
 +  * 2.25 compiled with ICC and Open MPI
 +
 +use  ''module avail tau'' to view installed versions.
 +
 +example :
 +
 +
 +
 +<code bash>
 +
 +$ module avail perf/tau
 +
 +</code>
 + 
 +===== TAU usage and displaying tools =====
 +
 +    - **Dynamic Instrumentation**: No change to your application's source or binary code is necessary. Using the tau_exec command before your executable generates both profile and trace data.
 +    - **Compiler-Based Instrumentation**: TAU can also be used to compile your application using wrapper scripts for ''mpicc'', ''mpicxx'', and ''mpif90''. Tau instruments the binary code without changing the source. Using the ''tau_exec'' command before the TAU-compiled executable generates profile and trace data. Data is collected on both ''MPI'' calls and your application's function calls.
 +
 +==== Dynamic Instrumentation ====
 +
 +
 +<note tip>  
 + Usefull env variables:
 +  * TAU_TRACE=1 (defaul 0) to view traces 
 +  * TAU_PROFILE=1 (default) 
 +  * TAU_COMM_MATRIX=1 default 0) to view 3D communication matrix
 +
 +</note>
 +
 +  - Load the needed tau <code bash>$ module load perf/tau/icc</code>
 +  - Compile <code bash>$ mpicc hello.c -o hello</code>
 +  - Dynamic instrumentation <code bash>$ mpirun -np $NSLOTS tau_exec ./hello</code> 
 +  - Run TAU's recompiling tool <code>$ tau_treemerge.pl</code>
 +  - After this it will have generated some output files, merge them with the next command <code bash>$ tau2slog2 tau.trc tau.edf -o tau.slog2</code>
 +  - Now just open the new merged file with the default displaying tool <code bash>$ jumpshot tau.slog2</code>
 +  - For profiling just call ''pprof'' and ''paraprof'' programs to view profilers results
 +
 +
 +==== Compiler-Based Instrumentation====
 + 
 +For each compiler type there is TAU wrapper, for example: 
 +
 +  * ''tau_cxx.sh'' for ''C++'' compiler
 +  * ''tau_f90.sh'' for Fortarn 90 compiler
 +  * ''tau_cc.sh'' fot C compiler
 +
 +Tau warapper uses ''$TAU_MAKEFILE'' to compile programs.  
 +
 +  - Compile programs <code bash>tau_cc.sh hello.c -o hello</code>
 +  - Run program as usual <code bash>mpirun -np $NSLOTS ./hello</code>
 +  - Follow steps 4, 5, 6 like for dynamic instrumentation
 +
 +You can also view profilers information with: ''pprof'' or ''paraprof''
 +
 +==== Example ====
 +
 +Let's profile/trace program (simple Jacobi iteration)
 +
 +
 +**Tracing**\\
 +
 +<code bash>
 +
 +$ module load perf/tau/icc
 +
 +$ mpicc jacobi.c -o jacobi
 +
 +$ mpirun -np 4 tau_exec ./jacobi
 +
 +$ tau_treemerge.pl
 +
 +$ tau2slog2 tau.trc tau.edf -o tau.slog2
 +
 +$ jumpshot tau.slog2
 +
 +</code>
 +
 +{{:tau1.png?300|}} {{:tau2.png?300 |}}
 +
 +
 +----
 +
 +
 +**Profiling**\\
 +We need to pack all the profiles.* files in a
 +unique one:
 +
 +<code bash>
 +
 +$ paraprof --pack tau.ppk
 +
 +</code>
 +Now, we can visualize the tau.ppk file by using
 +Paraprof
 +<code bash>
 +$ paraprof
 +</code>
 +
 +<note tip>click to enlarge</note>
 +
 +{{:profile.png?300|}} {{:profile2.png?300 |}}
  
  • outils_analyse/tau.1425044266.txt.gz
  • Dernière modification : 2015/02/27 13:37
  • de admin