So far in this series, we’ve covered an introduction to some Dataflow concepts and some of the Dataflow blocks that are available. Today we’ll look at some of the details to consider when building dataflow meshes.
I mentioned in my first Dataflow post that completion can be handled by calling
Complete, which will eventually cause the
Completion task to complete. This is the way to indicate successful completion. In a pipeline-style dataflow mesh, you can easily propagate this completion by ensuring the links have their
PropagateCompletion option set to
You can also complete a block with an error indication. To do this, call the block’s
Fault method. This will drop all currently-buffered items and cause the
Completion task to complete in a faulted state. However, if you propagate completion, then each block will wrap the previous block’s fault in an
AggregateException. In a pipeline mesh, this can leave you with a deeply nested exception coming out of the last block.
Finally, you can also cancel a block. Cancellation has similar semantics to faulting: when you cancel a block, it will drop all of its currently-buffered items and then its
Completion task will complete in a canceled state. To cancel a block, you must set a
CancellationToken in the options when constructing the block. Cancellation is most useful when shutting down an entire dataflow mesh.
Block Options: Parallel Processing
As I discussed last time, different blocks have different task configurations. Most blocks have at least one task that will spin up to push output data further along in the mesh, and some blocks have other tasks that do processing of the data - most notably
By default, each block will not process more than one item at a time. Each block is independent of other blocks, so one block may process one item while another block is processing another item, but each block limits itself to a single item at once. This behavior can be changed by setting
MaxDegreeOfParallelism in the options when constructing the block. When this is set to a value other than one, the “processing” blocks may process items using multiple tasks at once. The block will take care of ordering the results, so you don’t have to worry about parallel processing messing up the sequencing of the data.
Block Options: Synchronization
By default, each block is independent of other blocks, so one block may process one item while another block is processing another item. This provides some natural parallelism to the mesh as a whole. However, there are some cases where the processing done by one block must be exclusive to the processing done by another block. In these cases, you can specify the
TaskScheduler in the options when constructing the block.
This is where the
ConcurrentExclusiveSchedulerPair type (which I have blogged about before) is really useful. By applying the exclusive (or concurrent) scheduler to certain blocks in your dataflow, you can synchronize different parts of your mesh while allowing the rest of your mesh to benefit from the natural parallelism inherent in the default task scheduler.
Remember the standard caveat for
ConcurrentExclusiveSchedulerPair: it only applies while the task was executing. If the block is using an
async method, it is not considered “in” the scheduler while it is
You can also use the
TaskScheduler option to execute a block’s actions on a specific context captured by
TaskScheduler.FromCurrentSynchronizationContext. E.g., an
ActionBlock at the end of a mesh to update a user interface.
Block Options: Throttling Data
Almost every block has at least one buffer. If your dataflow is getting its source data from I/O, you’ll probably want to limit the buffering that goes on. Remember: different computers have different performance characteristics, and your computer may have a bottleneck in one part of your mesh while a client computer may have a bottleneck in a different part of your mesh. So, whenever you are looking at a potentially large amount of data, you should consider throttling the data buffers.
Each buffer can be limited by setting the
BoundedCapacity in the options when constructing the block. But the story doesn’t end there: you often need to limit all the following buffers in your mesh. A good understanding of the blocks and how they work is necessary to properly throttle data. Later in this series we’ll do some simple throttling of a producer/consumer queue, but for your own meshes you should thoroughly read and understand the Introduction to TPL Dataflow document.
Data throttling should be used when the data is coming from I/O, but there’s another important scenario as well: if you have a “T” in your dataflow mesh, you may need to set
BoundedCapacity to do load balancing. By default, any block will greedily buffer any data offered to it, so if you have (unfiltered) output going to multiple blocks, you’ll want to limit their buffers. We’ll look at an example of this a little later in this series.
Block Options: Throttling CPU Usage
By default, the “processing” blocks spin up one task (or several tasks if you’ve enabled parallelism) on the thread pool (or a specified scheduler if you’re using synchronization). This task will continue running in a loop as long as there is data available. This behavior is efficient, but it can cause some fairness issues if the data is continuous.
To mitigate this, you can set
MaxMessagesPerTask in the options when constructing the block. As the name implies, this value specifies the number of data items that an individual task will process. If there are more data items, the task will be recycled to continue processing. This is less efficient but more fair to other tasks in the system.
This introductory series on Dataflow is just scratching the surface. The resources below have much more information.
- Document: Introduction to TPL Dataflow
- Document: Guide to Implementing Custom TPL Dataflow Blocks
- TPL Dataflow forum
Update (2014-12-01): For more details, see Chapter 4 in my Concurrency Cookbook.