Intel® Trace Analyzer User's Reference Guide

Intel® Trace Analyzer User's Reference Guide
Figure 7.4. Comparing run A with 2 processes to run B with
4 processes
The message profile shows the quotient B/A of the average transfer rate. The rule
that the Comparison Message Profile (and in fact the whole Comparison View)
uses to map the senders and receivers of the two runs onto each other is quite
simple: child number i of run A's process aggregation is always compared with
(mapped to) child number i of run B's process aggregation.
Mapping of Functions
Functions of the two files A and B are mapped onto each other by their fully
qualified name. This name contains not only the mere function name, but a
hierarchical name that is constructed by the Intel® Trace Collector using any
information about modules, name spaces and classes that was available at trace
time.
For example the fully qualified name of MPI_Allreduce will be
MPI:MPI_Allreduce because Intel Trace Collector puts all MPI functions into the
group MPI. Function groups that were defined by the user in ITA have no influence
on these full function names. The function group editor described in the section
called “The Function Group Editor” shows the fully qualified name of a function
in a small tooltip window when the mouse hovers long enough over an entry.
The mapping of function groups is a little more subtle. For function groups that are
within the hierarchy of the automatically created function group “Major Function
Groups” in file A it is tried to find a matching group in B with the same name and
nesting level in the corresponding hierarchy in B.
For automatically generated groups this works quite good. For example MPI is
always mapped to MPI even if the groups differ because the two program runs
did use a different subset of MPI calls. The same is true for groups that were
created by instrumentation using the API provided by Intel Trace Collector.
When you create new function groups either by using the Function Group Editor
or the ubiquitous context menu entries to ungroup existing function groups for
one file then there will be created matching groups for the other file. You can
find these read only groups under the header “Generated Groups” in the Function
Group Editor.
Document number: 318120-002 92