Table of Contents
Advertisement
file. Enter a < CTRL> -D at the HP-UX prompt to return to the
Softkey Interface.
To run the performance measurement, enter the following
command:
performance_measurement_run 10 <RETURN>
The command above causes 10 traces to occur. The SPMT
processes the trace information after each trace, and the number of
the trace being processed is shown on the status line.
Enter the following command to cause the processed trace
information to be dumped to the "perf.out" file.
performance_measurement_end <RETURN>
Now, to generate a report from the "perf.out" file, type the
following on the command line to fork a shell and run the perf32
utility:
!perf32 | more
Information similar to the listing in figure 4-5 is scrolled onto your
display.
Two sets of information are given in the duration measurement
report: module duration and module usage. The first set is the
"module duration" measurement. (You can tell because the "from
address" is lower than the "to address".)
The module duration report in figure 4-5 shows that the average
amount of time it takes for the "math_library" module to execute is
roughly 82 microseconds.
Module usage measurements show how much time is spent outside
the module of interest; they indicate how often the module is used.
The report shown in the second part of figure 4-5 shows that there
is heavy demand for the "math_library" function. In fact, the time
between executions of the "math_library" module is generally less
than the amount of time it takes for the "math_library" module to
execute.
Performance Measurements 4-33
Advertisement
Table of Contents
