Troubleshooting: Performance Insufficient (Windows Embedded CE 6.0)
1/6/2010
When you create a Windows Embedded CE–based device, you can encounter problems with the performance of either the operating system (OS) or the target device. The following table shows descriptions of common problems and suggestions for resolving the problems.
| Description | Resolution |
|---|---|
Cannot gather sufficient data about OS performance |
Create a run-time image that supports the kernel profiler. You can use the kernel profiler to determine where the optimization of code provides the greatest benefit. For more information about the kernel profiler,see Kernel Profiler. |
Display does not function properly |
Verify that the display orientation for the target device is correct, and verify that the display driver is designed correctly. For more information, see Display Drivers and Shell OS Design Development. |
Memory use is not optimized |
Consider the type of memory that your target device uses. For more information, see RAM, ROM, and Mass Storage Comparison. |
Network driver is not optimized |
Create a network performance test, analyze the results of the test, and then make adjustments to improve the performance of your network driver. For more information, see Improving Performance of an NDIS Miniport Driver. |
OS design is difficult to work with because of its complexity |
Reduce the number of Catalog items included in the OS design. With fewer Catalog items, you may be able to design, test, and build a run-time image more quickly. You can restrict the number of Catalog items in your OS design by setting environment variables. For information about how to set an environment variable, see Setting or Clearing an Environment Variable (Visual Studio). |
Target device boots slowly |
Choose a registry type that is appropriate for the way that you use the target device. The registry type affects the performance of the target device, particularly during the boot sequence. For more information, see Registry Type Comparison. |