To reliably create high-performance programs, you need to understand the performance of the individual components you use. Thus, measurement has to be an integral part of the design process.
In the April 2008 issue of MSDN Magazine, Vance Morrison showed you how to quantify the expense of various .NET features so you know when it’s appropriate to use them.
In the May 2008 installment of the CLR Inside Out column, Vance continues his discussion of performance metrics, this time focusing on understanding what the numbers mean and predicting the performance of a component before you actually measure it.
Don’t forget to browse the sample code in our online code library.
Check out our MSDN Magazine archives for more about coding for performance.