Intel® Trace Analyzer and Collector

Filtering and Tagging

In the Event Timeline, you see the tagged functions in a frame and with their function labels in bold. The lines of the tagged messages and collective operations are thicker.

When you filter the Event Timeline for a particular process, you see only the MPI functions of this process, since only they pass the filter and all the other functions and processes are filtered out.

Mappings in Comparison Views

It is important to compare only comparable things. When comparing two program runs you can try to compare the time that a process A.P0 spent in a function in run A to the time of another process B.P0 in run B with or without caring for the fact that B.P0 did only half of the work because run B used twice as much processes.

General Description

Intel® Trace Collector configuration assistant provides a simple GUI interface to view and edit the Intel Trace Collector configuration files. It can also compute an average size of the trace file taking into account the modified parameters.

To launch the Intel® Trace Collector configuration assistant for trace.stf, type the following in the command line:

Recording Source Location Information

Intel® Trace Collector can automatically record the locations of subroutine calls in the source code. Compile the relevant application modules with support for debugging by using these compiler flags that enable the generation of debug information for Intel® Trace Collector:

mpicc -g -c ctest.c
mpif77 -g -c ftest.c

If your compiler does not support a flag, then search for a similar one.

Allinea* Distributed Debugging Tool

Allinea*'s Distributed Debugging Tool (DDT) must be configured to run the user's application with the necessary Intel libraries preloaded.

Take the following steps:

  • Go to the Run dialog box

  • Select the Session/Options menu

  • In the Session/Options menu, choose Intel MPI Library and the Submit through queue or configure own mpirun command option

Datatype Mismatches


Data type mismatches are detected by calculating a hash value of the data type signature and comparing that hash value: if the hash values are different, the type signatures must have been different too and an error is reported. Because the information about the full type signature at the sender is not available, it has to be deduced from the function call parameters and/or source code locations where the data is transmitted.

Suscribirse a Intel® Trace Analyzer and Collector