It's not uncommon for developers to make assumptions regarding the performance of an application. Frequently this is caused by not being given a performance target for operations based on real world load, during the design process. Therefore, we don't always develop tests to validate a design, proving that one design over another is better.
In a recent article from Bill Wagner, he provides a very good overview of the reasons that some collections are better than others, depending on what they contain, and how they are used. I strongly recommend reading that article here.
Perhaps in an upcoming post, I can outline some of basic differences between the generic collections that the .Net framework provides, including some examples of how their selection affects performance.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment