Export (0) Print
Expand All
0 out of 3 rated this helpful - Rate this topic

Remote Call Profiler (Windows CE 5.0)

Windows CE 5.0
Send Feedback

Remote Call Profiler combines profiling and analysis tools with a graphical interface that enables you to identify algorithmic bottlenecks in your code.

The technology in Remote 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 Remote Call Profiler. For more information, see Data Viewing in Remote Call Profiler.

With the Remote Call Profiler user interface, you can choose how you want to view and analyze collected data. Using the Remote Call Profiler Timeline Window, you can focus on a range of time within each profile run.

Remote 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, Remote 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 Remote Call Profiler Performance Data.

Run-time images built with Microsoft® Platform Builder 4.0 or later support Remote Call Profiler.

To collect data from an application, the version of Remote Call Profiler must match the version of the Windows CE OS upon which your run-time image is based. For example, you must use the version of Remote 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 Remote 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 Remote Call Profiler.

Note   You cannot run the Remote Call Profiler tool and the Remote Kernel Tracker tool simultaneously. For information about Remote Kernel Tracker, see Remote Kernel Tracker.

See Also

How to Use Remote Call Profiler to Find Performance Problems | Introduction to Remote Call Profiler


Send Feedback on this topic to the authors

Feedback FAQs

© 2006 Microsoft Corporation. All rights reserved.


Show:
© 2014 Microsoft. All rights reserved.