I l @ ve RuBoard |
In the previous chapter, I discussed methodologies for finding functional issues with your applications. In this chapter, we'll look at the some of the most common and significant causes of performance problems. Resolving performance issues in any application is not an easy task. You can think of this chapter as a "cheat sheet" for the most common issues. I'll cover a wide variety of topics, but this chapter will by no means be comprehensive. There are, after all, a virtually infinite number of ways to shoot yourself in the foot . My focus will be on the most common issues that developers need to worry about. But I'll also discuss some issues that are good to be aware of just for the sake of good programming practice. Whether you're investigating performance or resource problems in an existing application or designing a new product, the material in this chapter should provide an essential reference. In this chapter, you'll see a number of examples of compiled Microsoft intermediate language (MSIL) code because most of the performance problems I'll discuss are the result of bad programming practices or mistaken assumptions. Microsoft Visual Basic has always had a reputation for making development easier, but of course this often means that the compiler inserts a lot of code under the covers to implement those language features. I'll try to show you the implications of those features so you'll know what to avoid and so you can have another tool for analyzing your code. Note You don't have to understand MSIL in order to understand this chapter. I'll try to explain as much as necessary for the examples provided, and the material can serve as a starting point for your own investigations. However, it's important that you have at least a basic understanding of what the Visual Basic .NET compiler produces. This can help you to make better decisions.
|
I l @ ve RuBoard |