Timing Value Analysis

All Remote Call Profiler timing values exclude the time attributed to profiling probes and exclude the time spent writing to Remote Call Profiler data buffers.

The following table shows modifiers for the timing values that Remote Call Profiler calculates.

Application time is time that is spent specifically in your code. Application time excludes time spent in calls to the OS and time spent in other threads. Application time does not record transition events, or the time that your functions are blocked while waiting for a thread or input/output operation.

Elapsed time is the time that the system spends executing your code.

Application time and elapsed time are both valuable in the analysis of performance. Application time reveals the efficiency of your code, and elapsed time shows you how your code performs within the system.

Exclusive time is the time spent in a function. Exclusive time does not include the time spent in functions called by the function. You can analyze the performance of an individual function with exclusive time. Exclusive time may highlight a slower algorithm in a function because exclusive time ignores the contributions of subroutines. With exclusive time, at the beginning of an analysis of the performance of your code, you may uncover likely candidates for significant performance enhancement because your code may contain a number of functions that are not optimized.

Inclusive time is the time spent in a function and in the subroutines of the function. You can analyze the execution path of a complex algorithm with inclusive time. Inclusive time may highlight a branch of the call tree for code that consumes an excessive amount of time.

See Also

Remote Call Profiler Performance Data

 Last updated on Friday, October 08, 2004

© 1992-2003 Microsoft Corporation. All rights reserved.