Table of Contents
Advertisement
Note
Using the "perf32"
Report Generator
measurement, you must rename the perf.out file before performing
another measurement.
The "performance_measurement_end" command does not affect
the current performance measurement data which exists within the
emulation system. In other words, you can add more traces later to
the existing performance measurement by entering another
"performance_measurement_run" command.
Once you have entered the "performance_measurement_end"
command, you can use the perf32 report generator to look at the
data saved in the perf.out file.
The "perf.out" file is a binary file. Do not try to read it with the
HP-UX more or cat commands. The perf32 report generator
utility (described in the following section) must be used to read the
contents of the "perf.out" file.
The perf32 report generator utility must be used to read the
information in the "perf.out" file and other files dumped by the
SPMT (in other words, renamed "perf.out" files). The perf32 utility
is run from the HP-UX shell. You can fork a shell while in the
Softkey Interface and run perf32, or you can exit the Softkey
Interface and run perf32.
Options to "perf32"
A default report, containing all performance measurement
information, is generated when the perf32 command is used
without any options. The options available with perf32 allow you
to limit the information in the generated report. These options are
described below.
-h
Produce outputs limited to histograms.
-s
Produce a summary limited to the statistical
data.
Performance Measurements 4-11
Advertisement
Table of Contents
