Table of Contents
Advertisement
Activity
Measurements
Duration
Measurements
4-2 Performance Measurements
Activity measurements are measurements of the number of
accesses (reads or writes) within an address range. The SPMT
shows you the percentage of analyzer trace states that are in the
specified address range, as well as the percentage of time taken by
those states. Two types of activity are measured: memory activity,
and program activity.
Memory Activity
Memory activity is all activity that occurs within the address range.
Program Activity
Program activity is the activity caused by instruction execution in
the address range. Program activity includes opcode fetches and
the cycles that result from the execution of those instructions
(reads and writes to memory, stack pushes, etc.).
For example, suppose an address range being measured for activity
contains an opcode that causes a stack push, which results in
multiple write operations to the stack area (outside the range).
The memory activity measurement will count only the stack push
opcode cycle. However, the program activity measurement will
count the stack push opcode cycle and the write operations to the
stack.
By comparing the program activity and the memory activity in an
address range, you can get an idea of how much activity in other
areas is caused by the code being measured. An activity
measurement report of the code (prog), data, and stack sections of
a program is shown in figure 4-1.
Duration measurements provide a best-case/worst-case
characterization of code execution time. These measurements
record execution times that fall within a set of specified time
ranges. The analyzer trace command is set up to store only the
entry and exit states of the module to be measured (for example, a
C function or Pascal procedure). The SPMT provides two types of
duration measurements: module duration, and module usage.
Advertisement
Table of Contents
