When to use BlockingCollection and when ConcurrentBag instead of List?

by

You can indeed use a BlockingCollection, but there is absolutely no point in doing so.

First off, note that BlockingCollection is a wrapper around a collection that implements IProducerConsumerCollection<T>. Any type that implements that interface can be used as the underlying storage:

When you create a BlockingCollection<T> object, you can specify not
only the bounded capacity but also the type of collection to use. For
example, you could specify a ConcurrentQueue<T> object for first in,
first out (FIFO) behavior, or a ConcurrentStack<T> object for last
in,first out (LIFO) behavior. You can use any collection class that
implements the IProducerConsumerCollection<T> interface. The default
collection type for BlockingCollection<T> is ConcurrentQueue<T>.

This includes ConcurrentBag<T>, which means you can have a blocking concurrent bag. So what’s the difference between a plain IProducerConsumerCollection<T> and a blocking collection? The documentation of BlockingCollection says (emphasis mine):

BlockingCollection<T> is used as a wrapper for an
IProducerConsumerCollection<T> instance, allowing removal attempts
from the collection to block until data is available to be removed.
Similarly, a BlockingCollection<T> can be created to enforce an
upper-bound on the number of data elements allowed in the
IProducerConsumerCollection<T> […]

Since in the linked question there is no need to do either of these things, using BlockingCollection simply adds a layer of functionality that goes unused.

More Related Contents:

  1. Execute task in background in WPF application
  2. How to create a task (TPL) running a STA thread?
  3. The calling thread cannot access this object because a different thread owns it
  4. What is the difference between task and thread?
  5. How to use WPF Background Worker
  6. How do I update an ObservableCollection via a worker thread?
  7. What is the difference between Task.Run() and Task.Factory.StartNew()
  8. When to use Task.Delay, when to use Thread.Sleep?
  9. How to update GUI with backgroundworker?
  10. Accessing UI (Main) Thread safely in WPF
  11. Is Task.Factory.StartNew() guaranteed to use another thread than the calling thread?
  12. Cancelling a pending task synchronously on the UI thread
  13. How to execute task in the wpf background while able to provide report and allow cancellation?
  14. Does using Tasks (TPL) library make an application multithreaded?
  15. The current SynchronizationContext may not be used as a TaskScheduler
  16. The calling thread cannot access this object because a different thread owns it.WPF [duplicate]
  17. ConfigureAwait pushes the continuation to a pool thread
  18. Using BindingOperations.EnableCollectionSynchronization
  19. Can you access UI elements from another thread? (get not set)
  20. WPF UI multitasking
  21. How to achieve remove_if functionality in .NET ConcurrentDictionary
  22. Calling async methods from non-async code
  23. Error: Must create DependencySource on same Thread as the DependencyObject even by using Dispatcher
  24. WPF loading animation on a separate UI thread? (C#)
  25. Why CancellationToken is separate from CancellationTokenSource?
  26. Should i use ThreadPools or Task Parallel Library for IO-bound operations
  27. Synchronous implementation of interface that returns Task
  28. How to properly parallelise job heavily relying on I/O
  29. How to execute a method periodically from WPF client application using threading or timer [closed]
  30. Calling TaskCompletionSource.SetResult in a non blocking manner

Leave a Comment