---

Introduction to Code Speed Performance Guidelines

Contents:

Organization of This Document

For most users, performance means speed. If an application performs its tasks quickly, the user is happy. If an application performs tasks slowly or is unresponsive to commands, the user is likely going to get frustrated and may possibly not want to use that application.

The focus of this programming topic is improving the speed of your code, both in the real and perceived sense. In the real sense, you should measure the time it takes to complete operations and modify your algorithms and loop code to be as efficient as possible. In the perceived sense, you should make your application appear fast to the user, even if an operation actually takes a long time to complete.

Organization of This Document

This programming topic contains the following articles:

• “Diagnosing Slow Operations” describes techniques for finding which parts of your code are slow.

• “Check Your Algorithms” provides some guidelines on how to approach speed improvements in your code.

• “Impedance Mismatches” describes the performance impacts of translating between different data formats and tips on how to avoid such translations.

• “Perceived Responsiveness” describes ways to make your application feel faster than it may actually be.

• “Detecting Polling Behavior” describes a simple way to tell if your application is polling the system for information.

• “Accelerating Critical Code” provides some practical tips on how to improve the performance of iterative code.

• “Tuning for Specific Hardware” provides tips on how to tune your software for maximum performance on the G5 processor.

---