Trace Map enables you to zoom into the relevant subsets of large trace file Charts. It represents a miniature view of the MPI function activity over time. By default, the MPI function activity is shown in red color.
By default, the Flat Profile summarizes all major groups of functions and presents statistics over the processes. The exact contents of these groups depend on the group definitions stored in the trace file or you can define them by yourself. In the file poisson_icomm.single.stf, these are only MPI and Application groups.
To Do This:
Performance Assistant provides you with the general and detailed information about performance problems. You can use this feature either in GUI or in the CLI mode.
The seek and jump function enables you to go directly to a particular function event in the trace.
Use this function with the indexed tracefile format (ITF).
The General Preferences enable you to set up the basic Intel® Trace Analyzer behavior, such as the startup options, view style, confirmation before quitting the Intel Trace Analyzer and the number of the recently opened tracefiles.
This is a preview feature. A preview feature may be changed or removed in a future production release.
otf2-to-stf <options> <OTF2 file> --help --version
Use this utility to convert an OTF2 trace file to the STF format to be able to view the trace file in Intel® Trace Analyzer. After conversion the resulting file appears in the same directory as the input file.
To get more detailed information about your application, you can instrument and trace various user-defined events in your application, including non-MPI function calls. In practice, it is often useful to record entries and exits to/from functions or code regions within larger functions.
Use the following Intel® Trace Collector capabilities:
- Automatic function instrumentation with the compiler
Manual source code instrumentation with Intel® Trace Collector API
For TotalView* Debugger, it is necessary to pay attention that the breakpoint should be set for all processes. There are several ways to automate procedure of setting breakpoints. Mostly it depends on how commonly it is planned to use this automation.
If it is planned to apply it only for the current program, you can create the file filename.tvd (file name being the name of the executable) in the working directory in advance and put the following line into it:
int VT_tracestate (int * state)
Gets logging state of current thread.
Set by configuration options PROCESS/CLUSTER, modified by VT_traceon/off().
There are three states:
0 = thread is logging
1 = thread is currently not logging
2 = logging has been turned off completely
These are API calls that allow logging of message send and receive and MPI-style collective operations. Because they are modeled after MPI operations, they use the same kind of communicator to define the context for the operation.
Logging send/receive events evaluates the rank local within the active communicator, and matches events only if they take place in the same communicator (in other words, it is the same behavior as in MPI).