Code Profiling
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
Call Profiler begins recording profiling data when the OS loads the first instrumented module. Logging continues until the last process registered with the logger terminates.
With Call Profiler, you can use the Collection Control window to control the amount of data collected during a profiling run.
In the Collection Control window, you can start and stop profiling during the profiling run. Alternatively, you can insert Call Profiler data collection functions into your code before you compile the code.
You can use the data collection functions to specify where in the code to start and stop profiling.
Call Profiler profiles 10 processes and 32 threads by default. For information about setting the number of processes and threads to profile, see Choosing the Number of Processes and Threads to Profile.
Note
Call Profiler does not collect data for fibers. When a thread converts to a fiber, data collection for the thread stops. Call Profiler continues to collect data for other threads.
See Also
Concepts
Data Collection Control
Target Device Rebooting
Data Viewing in Call Profiler