tpl-dataflow

来源： https://stackoverflow.com/questions/39592534/tpl-dataflow-process-messages-from-two-incoming-blocks-sequentially

来源： https://stackoverflow.com/questions/39592534/tpl-dataflow-process-messages-from-two-incoming-blocks-sequentially

来源： https://stackoverflow.com/questions/50120304/request-response-pattern-with-tpl-dataflow

来源： https://stackoverflow.com/questions/50120304/request-response-pattern-with-tpl-dataflow

问题 I have worked with TPL dataflow. Really liked it. I had heard the term Akka many times from my java/scala friends so I tried to read about it and found out that akka has a .net port too. Great. When I continued reading about what akka is, I was surprised to see that it sounds exactly like TPL dataflow. So coming to my question, what is the difference between TPL dataflow and Akka.net ? When to chose what ? 回答1: Akka is an actor based model, and so is TPL Dataflow. As the latter is described

问题 I have a TransformManyBlock with the following design: Input: Path to a file Output: IEnumerable of the file's contents, one line at a time I am running this block on a huge file (61GB), which is too large to fit into RAM. In order to avoid unbounded memory growth, I have set BoundedCapacity to a very low value (e.g. 1) for this block, and all downstream blocks. Nonetheless, the block apparently iterates the IEnumerable greedily, which consumes all available memory on the computer, grinding

问题 I have a question about implementing pipeline using Dataflow TPL library. My case is that I have a software that needs to process some tasks concurrently. Processing looks like this: first we process album at global level, and then we go inside album and process each picture individually. Let's say that application has got processing slots and they are configurable (for the sake of example assume slots = 2). This means that application can process either: a) two albums on the same time b) one

问题 I am using TPL pipeline design together with Stephen Cleary's Try library In short it wraps value/exception and floats it down the pipeline. So even items that have thrown exceptions inside their processing methods, at the end when I await resultsBlock.Completion; have Status=RunToCompletion . So I need other way how to register faulted items. Here is small sample: var downloadBlock = new TransformBlock<int, Try<int>>(construct => Try.Create(() => { //SomeProcessingMethod(); return 1; }));

问题 I am using TPL pipeline design together with Stephen Cleary's Try library In short it wraps value/exception and floats it down the pipeline. So even items that have thrown exceptions inside their processing methods, at the end when I await resultsBlock.Completion; have Status=RunToCompletion . So I need other way how to register faulted items. Here is small sample: var downloadBlock = new TransformBlock<int, Try<int>>(construct => Try.Create(() => { //SomeProcessingMethod(); return 1; }));

问题 I am using TPL pipeline design together with Stephen Cleary's Try library In short it wraps value/exception and floats it down the pipeline. So even items that have thrown exceptions inside their processing methods, at the end when I await resultsBlock.Completion; have Status=RunToCompletion . So I need other way how to register faulted items. Here is small sample: var downloadBlock = new TransformBlock<int, Try<int>>(construct => Try.Create(() => { //SomeProcessingMethod(); return 1; }));