Tips for Integrating Optimization Into the Development Cycle (Continued)

Testing/Optimizing Reused Code
If you know you'll be reusing code, the first step in optimizing is to run this code "as is" and see how it works with your target processor, if it works at all. All notes taken here should begin your optimization record. Next, recompile the reused code, and again test it on the target processor. Then test it for secondary processors, if necessary.

This is where you select the correct development platform for the project, whether it's Java, .NET, C++, or whatever. Strategic thinking definitely comes into play here. Making sure your framework is optimized far ahead of time for best results is probably the most important strategic decision you will make.

Optimizing during programming and final overall app testing are the most important (and obvious) times to upgrade and speed-up code. You may want to build in at least a twice-weekly window for optimization. If you schedule it into the routine, perhaps near the end of the day at a predetermined point, it becomes an organic part of the process and makes QA that much more effective.

Thanks to Sunita P. Shenoy, Technical Marketing Manager, Intel Software Development Products, for her assistance in compiling the information for this article. Some information was gathered and updated from tutorials on the Optimization page on the Intel Developer Services site.

About the Author
Chris Preimesberger is an IT writer/researcher based in the San Francisco Bay Area.