Read about the test details in the previous post . After a few more various tests, the initialization time overhead is changing from time to time, and sometimes there isn’t an overhead whatsoever. However, the fact remains the same, the asynchronous invocation pattern shows most constant results in this specific case. My good friend Aelij Arbel pointed out another pattern of invocation using the Parallel Extensions TPL – the asynchronous API. I added it to the test as follows: static void CallServicesTasksAsync...
I've been playing around with the parallel extensions shipped as part of the .NET 4.0 and Visual Studio 2010 RC. Turning immutable atomic self-contained CPU-bound operations to run in parallel is pretty easy. However, as soon as you drill down to more complex executions, where issues such as memory sharing, allocations, delegates, false sharing, and synchronization mechanisms come in mind, you may have trouble finding the optimal parallel execution model for your code. I was interested in testing...