Difference between revisions of "TAU"

From UFRC
Jump to navigation Jump to search
Line 32: Line 32:
 
* tau
 
* tau
 
==System Variables==
 
==System Variables==
* HPC_{{#uppercase:{{#var:app}}}}_DIR - installation directory
 
* HPC_TAU_BIN - executable directory
 
* HPC_TAU_LIB - library directory
 
* HPC_TAU_DOC - examples directory
 
 
* TAU - Tau library directory
 
* TAU - Tau library directory
 +
* TAUROOT - installation directory
 
* TAU_MAKEFILE - default makefile
 
* TAU_MAKEFILE - default makefile
 
* TAU_METRICS = LINUXTIMERS:PAPI_FP_OPS:PAPI_L2_DCM
 
* TAU_METRICS = LINUXTIMERS:PAPI_FP_OPS:PAPI_L2_DCM
Line 42: Line 39:
 
* TAU_TRACE = 0
 
* TAU_TRACE = 0
 
* TAU_CALLPATH = 0
 
* TAU_CALLPATH = 0
 +
 +
* HPC_{{#uppercase:{{#var:app}}}}_DIR - installation directory
 +
* HPC_TAU_BIN - executable directory
 +
* HPC_TAU_LIB - library directory
 +
* HPC_TAU_DOC - examples directory
 
* HPC_PDT_DIR - installation directory
 
* HPC_PDT_DIR - installation directory
 
* HPC_PDT_BIN - executable directory
 
* HPC_PDT_BIN - executable directory

Revision as of 17:07, 4 March 2014

Description

Tau website  

  • TAU Performance System® is a portable profiling and tracing toolkit for performance analysis of parallel programs written in Fortran, C, C++, Java, Python.
  • TAU (Tuning and Analysis Utilities) is capable of gathering performance information through instrumentation of functions, methods, basic blocks, and statements. All C++ language features are supported including templates and namespaces. The API also provides selection of profiling groups for organizing and controlling instrumentation. The instrumentation can be inserted in the source code using an automatic instrumentor tool based on the Program Database Toolkit (PDT), dynamically using DyninstAPI, at runtime in the Java Virtual Machine, or manually using the instrumentation API.
  • TAU's profile visualization tool, paraprof, provides graphical displays of all the performance analysis results, in aggregate and single node/context/thread forms. The user can quickly identify sources of performance bottlenecks in the application using the graphical interface. In addition, TAU can generate event traces that can be displayed with the Vampir, Paraver or JumpShot trace visualization tools.

Required Modules

modules documentation

Serial

  • intel/2013
  • tau

Parallel (MPI)

  • intel/2013
  • openmpi
  • tau

System Variables

  • TAU - Tau library directory
  • TAUROOT - installation directory
  • TAU_MAKEFILE - default makefile
  • TAU_METRICS = LINUXTIMERS:PAPI_FP_OPS:PAPI_L2_DCM
  • TAU_PROFILE = 1
  • TAU_TRACE = 0
  • TAU_CALLPATH = 0
  • HPC_{{#uppercase:Tau}}_DIR - installation directory
  • HPC_TAU_BIN - executable directory
  • HPC_TAU_LIB - library directory
  • HPC_TAU_DOC - examples directory
  • HPC_PDT_DIR - installation directory
  • HPC_PDT_BIN - executable directory
  • HPC_PDT_INC - includes directory
  • PAPI_PERFMON_EVENT_FILE - default performance event log file.

For advanced use the pdt module can be loaded individually.