.NET Framework 4 Parallel Extensions Also Have Powerful Extras

.NET Framework 4 offers dozens of new classes, structures and enumerations to support many common parallelism scenarios. However, there are some additional scenarios not covered in the base classes that compose Parallel Extensions.

.NET Framework 4 includes the new Parallel Extensions. They offer the new task-based programming model, PLINQ (short for "Parallel Language Integrated Query") and many other features to tackle the multicore and manycore revolution. If you face one of these scenarios in which you have to make either simple or complex customizations to tailor the base classes to tackle certain specific requirements, be sure to check the scenarios covered by the new Parallel Extensions Extras.

Parallel Extensions Extras is a complementary project that isn't part of the .NET 4 classes but it has been developed by Microsoft. As these extras include the source code, you can also tailor them for your specific needs. The extras are a bit hidden because they are included in one of the projects within the Parallel Extension Samples. The direct link to download its recently updated latest version is http://code.msdn.microsoft.com/ParExtSamples/Release/ProjectReleases.aspx?ReleaseId=4179 . So, if you download these samples for parallel programming with .NET 4, you can find and inspect the "ParallelExtensionExtras" project that contains all the extras organized in many folders, as in the next picture that displays the contents for this project in Visual Studio 2010 Solution Explorer.

A typical situation that usually needs a customized scheduler is when you want to use many tasks to run a pipeline. Each task represents a stage for the pipeline and you want to make sure that the task scheduler dedicates a thread to support the execution of each task. To do so, you can use the ThreadPerTaskScheduler class, included in the ParallelExtensionExtras project. This class is a subclass of System.Threading.Tasks.TaskScheduler and provides a task scheduler that dedicates a thread per task. It simply starts a new thread to process the provided task. Thus, you can create the tasks that will compose each stage of the pipeline with the necessary parameters to specify this customized scheduler. The ThreadPerTaskScheduler class is one of the nine customized task schedulers provided by Parallel Extensions Extras.

There are many other additional examples and these classes are worth a deeper analysis with complete examples of how to take advantage of them. In future posts, I'll explain samples that cover their usage. Parallel Extensions Extras groups the classes in the following categories:

  • Coordination data structures in the "CoordinationDataStructures" folder.
  • Drawing in the "Drawing" folder.
  • Extensions in the "Extensions" folder.
  • Parallel algorithms in the "ParallelAlgorithms" folder.
  • Partitioners in the "Partitioners" folder.
  • Task schedulers in the "TaskSchedulers" folder.
  • Utils in the "Utils" folder.

.NET Framework 4 offers dozens of new classes, structures and enumerations to support many common parallelism scenarios.

View Article



Comments

  • There are no comments yet. Be the first to comment!

Leave a Comment
  • Your email address will not be published. All fields are required.

Top White Papers and Webcasts

  • Today's competitive marketplace requires the organization to frequently release and deploy applications at the pace of user demands, with reduced cost, risk, and increased quality. This book defines the basics of application release and deployment, and provides best practices for implementation with resources for a deeper dive. Inside you will find: The business and technical drivers behind automated application release and deployment. Evaluation guides for application release and deployment solutions. …

  • With JRebel, developers get to see their code changes immediately, fine-tune their code with incremental changes, debug, explore and deploy their code with ease (both locally and remotely), and ultimately spend more time coding instead of waiting for the dreaded application redeploy to finish. Every time a developer tests a code change it takes minutes to build and deploy the application. JRebel keeps the app server running at all times, so testing is instantaneous and interactive.

Most Popular Programming Stories

More for Developers

Latest Developer Headlines

RSS Feeds