background image
<< Performance Profiling Results | Applying Performance Profile Filters >>
<< Performance Profiling Results | Applying Performance Profile Filters >>

Performance Summary

Runtime Analysis
Performance Summary
This section of the report indicates, for each instrumented function, procedure or
method (collectively referred to as functions), the following data:
·
Calls: The number times the function was called
·
Function (F) time: The time required to execute the code in a function exclusive
of any calls to its descendants
·
Function+descendant (F+D) time: The total time required to execute the code in
a function and in any function it calls.
Note that since each of the descendants may have been called by other
functions, it is not sufficient to simply add the descendants' F+D to the caller
function's F. In fact, it is possible for the descendants' F+D to be larger than the
calling function's F+D. The following example demonstrates three functions
a
,
b
and
c
, where both
a
and
b
each call
c
once:
function F
F+D
a
5
15
b
5
15
c
20
20
The F+D value of
a
is less than the F+D of
c
. This is because the F+D of
a
(15)
equals the F of
a
(5) plus one half the F+D of
c
(20/2=10).
·
F Time (% of root) and F+D Time (% of root): Same as above, expressed in
percentage of total execution time
·
Average F Time: The average time spent executing the function each time it was
called
Performance Profiling SCI Dump Driver
In C and C++, you can dump profiling trace data without using standard I/O
functions by using the Performance Profiling Dump Driver API contained in the
atqapi.h file, which is part of the Target Deployment Port
To customize the Performance Profiling Dump Driver, open the Target Deployment
Port directory and edit the atqapi.h. Follow the instructions and comments included
in the source code.
83