4.5. FUNCTION FILTERING
Showing only MPI Functions
In this example only functions that contain the string “mpi” (not case sensitive) some-
where in their name are shown. Since only MPI functions start with “MPI” in their name
this filter setting shows all MPI functions and filters the others.
Figure 4.25: Showing only MPI
50
CHAPTER 4. PERFORMANCE DATA VISUALIZATION
Showing only Functions with at least 250 ms Duration
This example demonstrates the filtering of functions by their duration. Here only long
function occurrences with a minimum duration time of 250 ms are shown. All other
functions are filtered.
Figure 4.26: Showing only functions with more than 250 ms duration
51
4.5. FUNCTION FILTERING
Combining Function Name and Duration Rules
This example combines the two previous rules. First the “any” relation is used. Thus,
the filter shows all functions that have at least 250 ms duration time and additionally
also all “MPI” functions.
Figure 4.27: Combining rules using “any”
52
CHAPTER 4. PERFORMANCE DATA VISUALIZATION
The second example illustrates the usage of the “all” relation. Here all shown functions
have to satisfy both rules. Therefore the filter shows only “MPI” functions that have a
duration time of more than 250 ms.
Figure 4.28: Combining rules using “all”
53
4.5. FUNCTION FILTERING
Building Ranges with Number of Invocation Rules
The combination of rules also allows for the filtering of functions in a specified criteria
range. The following example filter setup shows all functions whose number of invoca-
tions lie inside the range between 2000 and 15000.
Figure 4.29: Show functions inside a specified range
54
CHAPTER 4. PERFORMANCE DATA VISUALIZATION
This example demonstrates the opposite behavior of the previous example. Here all
functions whose number of invocations lie outside the range between 2000 and 15000
are shown, i.e., functions with less than 2000 invocations and functions with more than
15000 invocations.
Figure 4.30: Show functions outside a specified range
55
5 Comparison of Trace Files
The comparison of trace files in Vampir extends existing functionality. That way the
user can best benefit from already gained analysis experience. For the comparison
of performance characteristics all common charts are provided. In order to effectively
compare multiple trace files, their zoom needs to be coupled and synchronized. For
comparison of selected areas of interest the trace files need to be freely shiftable in
time. This allows for arbitrary alignments of the trace files, and thus, enables compari-
son of user selected areas in the trace data.
Figure 5.1: Compare View
All comparison features are provided in the “Compare View” window, depicted in Fig-
ure 5.1.
This section introduces the “Compare View” window and explains its usage. It illus-
trates the functionality with the help of screen shots. For this purpose the comparison
56
CHAPTER 5. COMPARISON OF TRACE FILES
of three trace files is demonstrated step by step. The three example trace files shown
are measurements of one test application, performing ten iterations of simple calcula-
tions, run on three different machines.
5.1 Starting the Compare View
The fist step in order to compare trace files in Vampir is to load the respective files.
Each trace file can be loaded one after another via “File → Open...” in the main menu.
Figure 5.2 shows Vampir with three open trace files.
Figure 5.2: Vampir with three open trace files
Now, the “Compare View” can be opened. This is done from the main menu by select-
ing “Window → Compare Traces”, see Figure 5.3.
57
5.1. STARTING THE COMPARE VIEW
Figure 5.3: Vampir Window menu entries
Figure 5.4 shows the opened “Compare View”. As can be seen by the navigation
toolbars all three open trace files are included in the “Compare View”. The files in the
view are sharing one coupled zoom. The usage of charts and zooming in this view is
described in Section 5.2.
Figure 5.4: Open Compare View
58
CHAPTER 5. COMPARISON OF TRACE FILES
5.2 Usage of Charts
For the comparison of performance metrics the “Compare View” provides all common
charts of Vampir. In contrast to the ordinary “Trace View” the “Compare View” opens
one chart instance for each trace file, i.e., with three open trace files, one click on
the “Master Timeline” icon opens three ”Master Timeline” charts. Also, in order to
distinguish the same charts between the trace files, all charts belonging to one trace
file have a special individual background color. Figure 5.5 depicts a “Compare View”
with open “Master Timeline”, “Process Timeline”, and “Function Summary” charts.
Figure 5.5: Compare View with open charts
All charts work the same way as in the “Trace View”. Due to the fact that the “Com-
pare View” couples the zoom of all trace files, the charts can be used to compare
performance characteristics.
As can be seen in Figure 5.5, trace A has the biggest duration time. The duration of
59
Dostları ilə paylaş: |