Call Profiler Performance Data
Other versions of this page are also available for the following:
.gif "A hyphen indicates that the information in this topic is not relevant for this platform, or that the platform does not support the API that is listed.")
.gif "A checkmark indicates that the information in this topic is relevant for this platform, and that any API listed is also supported on this platform.")
8/27/2008
During a profiling run, the Remote Call Profiler logging engine collects data when the profiled system enters a function and when the profiled system exits a function. By default, the elapsed time for an event is measured in CPU clock cycles.
For each function, Remote Call Profiler calculates up to 48 values that show elapsed and application time for the defined counters.
Remote Call Profiler displays totals for both the time spent exclusively in the function and the time spent in subroutines of the function.
For more information about timing values, see Timing Value Analysis.
For information about the various pieces of data that Remote Call Profiler collects, see Event Timing.
Note
Remote Call Profiler uses the QueryPerformanceCounter function from the board support package (BSP) to obtain timestamp information. If the timestamp information that the BSP provides is not adequately granular, performance timing might not be accurate, especially for an application that runs for a short period of time.
See Also
Concepts
Suppressed and Ignored Functions
Actual and Calculated Timing