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 [2016/01/29 12:45] – adminoutils_analyse:tau [2016/04/22 09:04] (Version actuelle) – admin
Ligne 1: Ligne 1:
 ====== TAU ====== ====== TAU ======
-FIXME 
- 
 TAU is an MPI program analyzer. It generates all necessary information during the program 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. execution, so that it can be read after it and displayed by a specialized program.
Ligne 9: Ligne 7:
 ===== Installed version ===== ===== Installed version =====
  
-  * 2.23 compiled with GCC and Open MPI +  * 2.25 compiled with GCC and Open MPI 
-  * 2.23 compiled with ICC and Open MPI+  * 2.25 compiled with ICC and Open MPI
  
 use  ''module avail tau'' to view installed versions. use  ''module avail tau'' to view installed versions.
Ligne 20: Ligne 18:
 <code bash> <code bash>
  
-$ module avail tau +$ module avail perf/tau
- +
-tau/ompi-gcc/2.23          tau/ompi-icc/2.23(default)+
  
 </code> </code>
Ligne 28: Ligne 24:
 ===== TAU usage and displaying tools ===== ===== 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. +    - **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.+    - **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 ==== ==== Dynamic Instrumentation ====
  
  
-<note tip>To display profile files we need to enable it first:<code> export TAU_PROFILE=1</code></note>+<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 tau</code>+  - Load the needed tau <code bash>$ module load perf/tau/icc</code>
   - Compile <code bash>$ mpicc hello.c -o hello</code>   - Compile <code bash>$ mpicc hello.c -o hello</code>
   - Dynamic instrumentation <code bash>$ mpirun -np $NSLOTS tau_exec ./hello</code>    - Dynamic instrumentation <code bash>$ mpirun -np $NSLOTS tau_exec ./hello</code> 
Ligne 70: Ligne 72:
 <code bash> <code bash>
  
-$ module load tau+$ module load perf/tau/icc
  
-$ mpicc jacobi.s -o jacobi+$ mpicc jacobi.c -o jacobi
  
 $ mpirun -np 4 tau_exec ./jacobi $ mpirun -np 4 tau_exec ./jacobi
  • outils_analyse/tau.1454071522.txt.gz
  • Dernière modification : 2016/01/29 12:45
  • de admin