Call Profiler (Windows Embedded CE 6.0)
Call Profiler combines profiling and analysis tools with a graphical interface that enables you to identify algorithmic bottlenecks in your code.
To use Call Profiler from Windows Embedded CE, you must first connect to the target device with Platform Manager. For more information about how to connect a remote tool to a target device with Platform Manager, see Remote Tool Connectivity.
The technology in Call Profiler provides a graphical environment to display the information you want to analyze. You can compare information from different sections of your data and view your data in a variety of formats with Call Profiler. For more information, see Data Viewing in Call Profiler.
With the Call Profiler user interface, you can choose how you want to view and analyze collected data. Using the Call Profiler Timeline Window, you can focus on a range of time within each profile run.
Call Profiler supports cross-process and cross-thread profiling and the use of user-defined performance counters. For more information, see Code Profiling.
During each profiling run, Call Profiler collects elapsed time and application time measurements.
Elapsed time measures the change in time during the execution of a function, including time spent in the OS and background threads.
Application time measures the time spent in the code for a function. For more information, see Call Profiler Performance Data.
Run-time images built with Microsoft® Platform Builder 4.0 or later support Call Profiler.
To collect data from an application, the version of Call Profiler must match the version of the Windows Embedded CE OS upon which your run-time image is based. For example, you must use the version of Call Profiler that shipped with Windows CE .NET 4.0 to collect data from an application that runs on a Windows CE .NET 4.0–based run-time image.
To use the Call Profiler tool with a run-time image, the OS design must include the corestra component. The corestra component supports the ASCII version of string handling.
Some design templates do not include the corestra component. For example, a run-time image based on the Tiny Kernel design template does not support Call Profiler.
|You cannot run the Call Profiler tool and the Kernel Tracker tool simultaneously. For information about Kernel Tracker, see Remote Kernel Tracker.|