Most of the time my "heavy computation" is async. Or I have many small operations which I need to use on the collection. How would I do that with PLINQ?
PLINQ is best suited for long-running CPU-bound operations. If you’re dealing with many small operations or asynchronous computations (sending HTTP requests for example) then async await with Task.WhenAll is a better choice over PLINQ
Great content, the difference between this and await Task.When all is that as Parallel is better to use with heavy and few computation, and task.whenall is better for "parallel" i/o operations?
This is great. I'm love using LINQ and this will certainly help make more performant LINQ queries. I assume Parallel foreach loops are still faster? Though the difference is probably smaller compared to sequential LINQ and foreach. What is the performance impact for ordering? Since .AsParallel() doesn't necessarily use Parallelism, do you recommend to add it to any LINQ-Query by default? Though if that were the case, Microsoft probably would've implemented it that way anyways.
can we alternate between threads with PLINQ, like one method print "ping" the other print "pong" and get an output : "ping pong ping pong ping pong ..." ? thanks for the video :D
What do you mean by the sentence do you a favor and don't use pink in your applications because you need to be familiar with how things work under the hod ?
Adding "AsParallel" without knowing how PLINQ works will likely introduce bugs or make your code even slower. It's important to understand how PLINQ actually works to know how to use it correctly.
