Timing Value Analysis
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
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.
| Modifier | Description |
|---|---|
Application Inclusive |
Includes subroutines and excludes transition events |
Application Exclusive |
Excludes subroutines and excludes transition events |
Elapsed Inclusive |
Includes subroutines and includes transition events |
Elapsed Exclusive |
Excludes subroutines and includes transition events |
The following are important points to remember about these modifiers:
- Application time is time 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 the system spends executing your code.
- Application time and elapsed time are 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 might 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 might uncover likely candidates for significant performance enhancement because your code might 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 might highlight a branch of the call tree for code that uses an excessive amount of time.