June 29, 2011 Leave a comment
The .NET Base Class Library (BCL) has a wide array of collection classes at your disposal which make it easy to manage collections of objects. While it’s great to have so many classes available, it can be daunting to choose the right collection to use for any given situation. As hard as it may be, choosing the right collection can be absolutely key to the performance and maintainability of your application!
This post will look at breaking down any confusion between each collection and the situations in which they excel. We will be spending most of our time looking at the System.Collections.Generic namespace, which is the recommended set of collections.
The Generic Collections: System.Collections.Generic namespace
The generic collections were introduced in .NET 2.0 in the System.Collections.Generic namespace. This is the main body of collections you should tend to focus on first, as they will tend to suit 99% of your needs right up front.
It is important to note that the generic collections are unsynchronized. This decision was made for performance reasons because depending on how you are using the collections its completely possible that synchronization may not be required or may be needed on a higher level than simple method-level synchronization. Furthermore, concurrent read access (all writes done at beginning and never again) is always safe, but for concurrent mixed access you should either synchronize the collection or use one of the concurrent collections.
So let’s look at each of the collections in turn and its various pros and cons, at the end we’ll summarize with a table to help make it easier to compare and contrast the different collections.
The Associative Collection Classes
Associative collections store a value in the collection by providing a key that is used to add/remove/lookup the item. Hence, the container associates the value with the key. These collections are most useful when you need to lookup/manipulate a collection using a key value. For example, if you wanted to look up an order in a collection of orders by an order id, you might have an associative collection where they key is the order id and the value is the order.
The Dictionary is probably the most used associative container class. The Dictionary is the fastest class for associative lookups/inserts/deletes because it uses a hash table under the covers. Because the keys are hashed, the key type should correctly implement GetHashCode() and Equals() appropriately or you should provide an external IEqualityComparer to the dictionary on construction. The insert/delete/lookup time of items in the dictionary is amortized constant time – O(1) – which means no matter how big the dictionary gets, the time it takes to find something remains relatively constant. This is highly desirable for high-speed lookups. The only downside is that the dictionary, by nature of using a hash table, is unordered, so you cannot easily traverse the items in a Dictionary in order.
The SortedDictionary is similar to the Dictionary in usage but very different in implementation. The SortedDictionary uses a binary tree under the covers to maintain the items in order by the key. As a consequence of sorting, the type used for the key must correctly implement IComparable so that the keys can be correctly sorted. The sorted dictionary trades a little bit of lookup time for the ability to maintain the items in order, thus insert/delete/lookup times in a sorted dictionary are logarithmic – O(log n). Generally speaking, with logarithmic time, you can double the size of the collection and it only has to perform one extra comparison to find the item. Use the SortedDictionary when you want fast lookups but also want to be able to maintain the collection in order by the key.
The SortedList is the other ordered associative container class in the generic containers. Once again SortedList, like SortedDictionary, uses a key to sort key-value pairs. Unlike SortedDictionary, however, items in a SortedList are stored as an ordered array of items. This means that insertions and deletions are linear – O(n) – because deleting or adding an item may involve shifting all items up or down in the list. Lookup time, however is O(log n) because the SortedList can use a binary search to find any item in the list by its key. So why would you ever want to do this? Well, the answer is that if you are going to load the SortedList up-front, the insertions will be slower, but because array indexing is faster than following object links, lookups are marginally faster than a SortedDictionary. Once again I’d use this in situations where you want fast lookups and want to maintain the collection in order by the key, and where insertions and deletions are rare.
The Non-Associative Containers
The other container classes are non-associative. They don’t use keys to manipulate the collection but rely on the object itself being stored or some other means (such as index) to manipulate the collection.
The List is a basic contiguous storage container. Some people may call this a vector or dynamic array. Essentially it is an array of items that grow once its current capacity is exceeded. Because the items are stored contiguously as an array, you can access items in the List by index very quickly. However inserting and removing in the beginning or middle of the List are very costly because you must shift all the items up or down as you delete or insert respectively. However, adding and removing at the end of a List is an amortized constant operation – O(1). Typically List is the standard go-to collection when you don’t have any other constraints, and typically we favor a List even over arrays unless we are sure the size will remain absolutely fixed.
The LinkedList is a basic implementation of a doubly-linked list. This means that you can add or remove items in the middle of a linked list very quickly (because there’s no items to move up or down in contiguous memory), but you also lose the ability to index items by position quickly. Most of the time we tend to favor List over LinkedList unless you are doing a lot of adding and removing from the collection, in which case a LinkedList may make more sense.
The HashSet is an unordered collection of unique items. This means that the collection cannot have duplicates and no order is maintained. Logically, this is very similar to having a Dictionary where the TKey and TValue both refer to the same object. This collection is very useful for maintaining a collection of items you wish to check membership against. For example, if you receive an order for a given vendor code, you may want to check to make sure the vendor code belongs to the set of vendor codes you handle. In these cases a HashSet is useful for super-quick lookups where order is not important. Once again, like in Dictionary, the type T should have a valid implementation of GetHashCode() and Equals(), or you should provide an appropriate IEqualityComparer to the HashSet on construction.
The SortedSet is to HashSet what the SortedDictionary is to Dictionary. That is, the SortedSet is a binary tree where the key and value are the same object. This once again means that adding/removing/lookups are logarithmic – O(log n) – but you gain the ability to iterate over the items in order. For this collection to be effective, type T must implement IComparable or you need to supply an external IComparer.
Finally, the Stack and Queue are two very specific collections that allow you to handle a sequential collection of objects in very specific ways. The Stack is a last-in-first-out (LIFO) container where items are added and removed from the top of the stack. Typically this is useful in situations where you want to stack actions and then be able to undo those actions in reverse order as needed. The Queue on the other hand is a first-in-first-out container which adds items at the end of the queue and removes items from the front. This is useful for situations where you need to process items in the order in which they came, such as a print spooler or waiting lines.
The Original Collections: System.Collections namespace
The original collection classes are largely considered deprecated by developers and by Microsoft itself. In fact they indicate that for the most part you should always favor the generic or concurrent collections, and only use the original collections when you are dealing with legacy .NET code.
Because these collections are out of vogue, let’s just briefly mention the original collection and their generic equivalents:
A dynamic, contiguous collection of objects.
Favor the generic collection List instead.
Associative, unordered collection of key-value pairs of objects.
Favor the generic collection Dictionary instead.
First-in-first-out (FIFO) collection of objects.
Favor the generic collection Queue instead.
Associative, ordered collection of key-value pairs of objects.
Favor the generic collection SortedList instead.
Last-in-first-out (LIFO) collection of objects.
Favor the generic collection Stack instead.
In general, the older collections are non-type-safe and in some cases less performant than their generic counterparts. Once again, the only reason you should fall back on these older collections is for backward compatibility with legacy code and libraries only.
The Concurrent Collections: System.Collections.Concurrent namespace
The concurrent collections are new as of .NET 4.0 and are included in the System.Collections.Concurrent namespace. These collections are optimized for use in situations where multi-threaded read and write access of a collection is desired.
The concurrent queue, stack, and dictionary work much as you’d expect. The bag and blocking collection are more unique. Below is the summary of each with a link to a blog post I did on each of them.
Thread-safe version of a queue (FIFO).
For more information see: C#/.NET Little Wonders: The ConcurrentStack and ConcurrentQueue
Thread-safe version of a stack (LIFO).
For more information see: C#/.NET Little Wonders: The ConcurrentStack and ConcurrentQueue
Thread-safe unordered collection of objects.
Optimized for situations where a thread may be bother reader and writer.
For more information see: C#/.NET Little Wonders: The ConcurrentBag and BlockingCollection
Thread-safe version of a dictionary.
Optimized for multiple readers (allows multiple readers under same lock).
For more information see C#/.NET Little Wonders: The ConcurrentDictionary
Wrapper collection that implement producers & consumers paradigm.
Readers can block until items are available to read.
Writers can block until space is available to write (if bounded).
For more information see C#/.NET Little Wonders: The ConcurrentBag and BlockingCollection
The .NET BCL has lots of collections built in to help you store and manipulate collections of data. Understanding how these collections work and knowing in which situations each container is best is one of the key skills necessary to build more performant code. Choosing the wrong collection for the job can make your code much slower or even harder to maintain if you choose one that doesn’t perform as well or otherwise doesn’t exactly fit the situation.
Remember to avoid the original collections and stick with the generic collections. If you need concurrent access, you can use the generic collections if the data is read-only, or consider the concurrent collections for mixed-access if you are running on .NET 4.0 or higher.