Level: Intermediate to Advanced
Ted Neward
Director, Developer Relations
Smartsheet.com
With the advent and growing ubiquity of multi-core CPUs, it has become clear: Concurrency is the dragon that programmers must slay in the coming decade, and unfortunately, the current crop of languages in widespread use-the imperative, object-oriented C-family of languages consisting of C++, Java and C<--simply aren't up to the task of handling concurrency easily. Instead, they defer the concurrency responsibilities to the developer, forcing programmers to reason about their code and its throughput and safety on every line. This is an unacceptable solution, and Microsoft has begun work to offer better ones in the next release of .NET 4.0. Nicknamed the "parallel extensions" to .NET, sometimes also referred to as "PLINQ", these extensions offer developers a simpler model for building multi-core-friendly applications, and in this session, we'll spend some time with the parallel extensions, how they work, and where to best utilize them.
You will learn:
- Various ways to parallelize .NET code
- How to recognize the different idioms for parallelizing code
- When not to parallelize code