This situation is fairly common: you need to re-use the same class over and over and you wish you didn’t have to pay the price for multiple allocations and garbage collection. The .NET framework doesn’t come with a generic pool class unfortunately so you have to create your own. I’ve seen very complicated implementations as well as others that weren’t thread-safe.
The following generic implementation relies on the .NET 4.0 ConcurrentBag<T> for storage which is thread-safe. The capacity parameter specifies the initial capacity of the pool.
As more objects are requested, new instances will be created. Note that the Take and Add methods are virtual if you need to perform some specific logic when taking or re-adding an object to the pool. You can also implement the IProducerConsumerCollection<T> interface in the ConcurrentPool if this is something you need (I’ve omitted it to keep this article short).
Any other IProducerConsumerCollection could be used as the underlying collection (ConcurrentQueue or ConcurrentStack for example). I’ve used the ConcurrentBag here because it provides the best performance out of those 3 for retrieval from what I’ve measured.