• 2019 Update 7
  • 03/31/2020

Tracing Applications

Intel® MPI Library Developer Guide for Linux* OS
Intel® MPI Library provides a variety of options for analyzing MPI applications. Some of these options are available within the Intel MPI Library, while some require additional analysis tools. For such tools, Intel MPI Library provides compilation and runtime options and environment variables for easier interoperability.
Intel® MPI Library provides tight integration with the Intel® Trace Analyzer and Collector, which enables you to analyze MPI applications and find errors in them. Intel® MPI Library has several compile- and runtime options to simplify the application analysis. Apart from the Intel Trace Analyzer and Collector, there is also a tool called Application Performance Snapshot intended for a higher level MPI analysis.
Both of the tools are available as part of the Intel® Parallel Studio XE Cluster Edition. Before proceeding to the next steps, make sure you have these product installed.

High-Level Performance Analysis

For a high-level application analysis, Intel provides a lightweight analysis tool Application Performance Snapshot (APS), which can analyze MPI and non-MPI applications. The tool provides general information about the application, such as MPI and OpenMP* utilization time and load balance, MPI operations usage, memory and disk usage, and other information. This information enables you to get a general idea about the application performance and identify spots for a more thorough analysis.
Follow these steps to analyze an application with the APS:
  1. Set up the environment for the compiler, Intel MPI Library and APS:
    $ source
    /compilers_and_libraries_<version>.<update>.<package>/linux/bin/compilervars.sh intel64 $ source
  2. Run your application with the
    option of
    $ mpirun -n 4 -aps ./myprog
    APS will generate a directory with the statistics files
  3. Launch the
    tool and pass the generated statistics to the tool:
    $ aps-report ./aps_result_<date>-<time>
    You will see the analysis results printed in the console window. Also, APS will generate an HTML report
    containing the same information.
For more details, refer to the
Application Performance Snapshot User's Guide

Tracing Applications

To analyze an application with the Intel Trace Analyzer and Collector, first you need generate a trace file of your application, and then open this file in Intel® Trace Analyzer to analyze communication patterns, time utilization, etc. Tracing is performed by preloading the Intel® Trace Collector profiling library at runtime, which intercepts all MPI calls and generates a trace file. Intel MPI Library provides the
) option to simplify this process.
Complete the following steps:
  1. Set up the environment for the Intel MPI Library and Intel Trace Analyzer and Collector:
    $ source
    /intel64/bin/mpivars.sh $ source
  2. Trace your application with the Intel Trace Collector:
    $ mpirun -trace -n 4 ./myprog
    As a result, a trace file
    is generated. For the example above, it is
  3. Analyze the application with the Intel Trace Analyzer:
    $ traceanalyzer ./myprog.stf &
The workflow above is the most common scenario of tracing with the Intel Trace Collector. For other tracing scenarios, see the Intel Trace Collector documentation.

Product and Performance Information


Intel's compilers may or may not optimize to the same degree for non-Intel microprocessors for optimizations that are not unique to Intel microprocessors. These optimizations include SSE2, SSE3, and SSSE3 instruction sets and other optimizations. Intel does not guarantee the availability, functionality, or effectiveness of any optimization on microprocessors not manufactured by Intel. Microprocessor-dependent optimizations in this product are intended for use with Intel microprocessors. Certain optimizations not specific to Intel microarchitecture are reserved for Intel microprocessors. Please refer to the applicable product User and Reference Guides for more information regarding the specific instruction sets covered by this notice.

Notice revision #20110804