Table of Contents
Advertisement
Note
4-32 Performance Measurements
If you are making duration measurements on a function that is
recursive, or one that has multiple entry and/or exit points, you
may wind up with invalid information.
Example Duration Measurement
The following examples assume that the SPMT demo program has
been loaded into the emulator and is executing.
display trace depth 512 <RETURN>
trace after math_library start or
math_library end only math_library start or
math_library end <RETURN>
The "trace" specification sets up the analyzer to capture only the
states that contain the start address of the "math_library" function
or the end address of the "math_library" function. Since the trigger
state is also stored, the analyzer is set up to trigger on the entry or
exit address of the "math_library" function. With these states in
memory, the analyzer will derive two measurements: time from
start to end of math_library, and time from end to start of
math_library.
Enter the following command to initialize the duration
measurement:
performance_measurement_initialize
time_ranges duration <RETURN>
The "time_ranges" file contains:
1 us 20 us
21 us 40 us
41 us 60 us
61 us 80 us
81 us 100 us
101 us 120 us
121 us 140 us
141 us 160 us
161 us 180 us
181 us 200 us
201 us 5 ms
You can fork a shell to HP-UX (by entering "! < RETURN> " on
the Softkey Interface command line) and create the "time_ranges"
Advertisement
Table of Contents
