Summary

In this chapter, you have seen how to measure performance and track down parallel bugs. The Visual Studio 2010 tools can be very helpful, but to get the best from them, you need to have a good understanding of the kinds of problems that can arise. I have listed some of the most common problems in each chapter as we have moved through this book, but you will find that your personal coding style leads you to create patterns of problems that you will have to track down and fix. The best advice I can give you is not to give up. Spending hours chasing down an intermittent issue can be exceptionally painful, but you will learn a huge amount as you do so. Over time, you will get a feel for what lies behind the problems are you looking for and your ability to locate and fix parallel defects will become much better—and, on occasion, you will find that hunting down a particularly elusive error can even be enjoyable.

0 0

Post a comment