Deciding when to stay sequential C#. NET

It may seem odd to emphasize the value of sequential execution in a book about parallel programming, but effective parallel programmers know when to leave well enough alone. Some problems are inherently sequential in nature—there are no pieces of work that can be performed concurrently. Some problems require so much coordination that the overhead incurred by parallel execution cancels out the performance gains. Some problems come with a mass of legacy code that would require too much rewriting to integrate with parallel code.

One of the most important times to consider sequential execution is when something is wrong with your parallel code and you can’t work out why. There are some new parallel features in the Visual Studio 2010 debugger that can be very helpful in tracking down bugs, but sometimes you need to go back to the basics to make sure that you are able to code a solution that works at all.


All rights reserved © 2018 Wisdom IT Services India Pvt. Ltd DMCA.com Protection Status

C#. NET Topics