Special Edition Using® Microsoft® ASP.NET

Tips and Tricks

Here’s my first, and probably strongest, recommendation: Don’t wait until the end of an application’s development to test its performance. Of course, with a project manager breathing down your neck for completion of the various pieces, performance testing is the last thing on your mind. But you might not be able to make changes in the code if you’re close to the end because of what else might break in the process.

If you performance test early in the game, code changes will have a minimal effect on other pieces of code. But after the codebase grows, more code depends on each different piece of code. It’s best to performance test before code has too many dependencies.

Another suggestion is to use the ASP.NET trace feature for ...