| Software Optimization Cookbook - High-Performance Recipes for the Intel Architecture (2002) |
| Front Cover | Book Details | |||||||||||||||
|
|
| Plot |
| From Book News, Inc. This book/CD-ROM package provides recipes for high-performance applications on the Intel Pentium III and Pentium 4 processors. Simple explanations and C language examples show how to address performance issues with algorithms, memory matching, branching, SIMD instructions, multiple threads, and floating point calculations. The book shows how to use performance tools to analyze and improve applications, how to identify which portions of an application should be given priority for optimizations, and how to design an application from the ground up. Some actual food recipes are included as well. Gerber is a software engineer.Copyright © 2004 Book News, Inc., Portland, OR About the Author Richard Berber joined Intel in 1991, and through years of learning-by-doing, he has become an expert in performance programming and optimizations. He has worked on numerous multimedia projects, 3D libraries, and computer games. As a software engineer, he works on the Intel® VTune™ Performance Analyzer and trains developers on optimization techniques. Book Description Revealing the secrets of the software tuning process, The Software Optimization Cookbook provides recipes for high-performance applications on the Intel® Pentium® III and Pentium® 4 processors. Simple explanations and C language examples show you how to address performance issues with algorithms, memory access, branching, SIMD instructions, multiple threads, and floating-point calculations. With this book, you need not be a processor architect or assembly language expert to get the full power out of your software on the 32-bit Intel Architecture. Learn how to: Use performance tools and tested concepts to analyze and improve applications. Determine which portions of an application should be given highest priority for optimizations. Identify the reasons that certain portions of your application are slower than they should be. Improve an application by working directly on the root cause of a software bottleneck. Design an application from the ground up for maximum performance. |
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||