Posted By: Charles | Jun 5th @ 10:06 AM

Parallel Extensions simplifies development by providing library-based support for introducing concurrency into applications written with any .NET language, including C# and Visual Basic. It includes the Task Parallel Library (TPL), which provides imperative data and task parallelism; Parallel LINQ (PLINQ), which provides declarative data parallelism; and all new Coordination Data Structures (CDS), which provide support for work coordination and managing shared state.

In addition to CDS, this upgrade provides several improvements, including a new scheduler that is more robust, efficient, and scalable. TPL also exposes new functionality, including methods for continuations. PLINQ now runs on top of TPL, clarifies order-preservation, and provides several new operators.

The June CTP works with the .NET Framework 3.5 as a simple, small-footprint installation that drops a single DLL, documentation, samples, and registers the DLL with Visual Studio 2008.

Here, we meet some of the key engineers of the Microsoft Parallel Computing Platform (which includes the Parallel Extensions for .NET...): Lead Developer Joe Duffy, Developer Huseyin Yildiz, Developer Igor Ostrovsky, Program Manager Stephen Toub and Program Manager Ed Essey.

We dig deeply into a lot of topics related to parallelism and conconcurency and how the new additions to the platform enable developers to exploit multi/many core processors in an elegant way.

Enjoy part 1. Part 2 is here.

Rating:
1
0
Where is Anders Hejlsberg?
Johannes
Johannes
Johannes Hansen, Denmark
Was blank the first time I saw the comment too, but now it shows up fine... An Edit perhaps?

Edit: Nope he didn't edit it... Now it's blank again?
Anders was very instrumental in getting Parallel Extensions off the ground and designed right.  He's still involved regularly on hard design problems, but is a busy guy and works on a lot of things across the company.

---joe
To Charles and Joe;

Thanks for the reply. I'm sure Andres has left the Parallel Ext in good hands!

..Ben
aL_
aL_
mm.. linq.. *arrggha*
cool cool Smiley i like the lazyinit Alot Smiley no more

public TheThing{
get{
if(thing_ == null)
 thing_ = new Thing();

return thing_;
}
}

for me Big Smile

got  a question though, how does the tpl relate to the ccr? was the ccr more of a incubation project? or does tpl replace ccr?

and another thing (nagging a bit here Smiley ) what happend to the accelerator project? Smiley (the gpu accelerated library) it seems it whould fit in very well in tpl Smiley and it was soo cool Big Smile love to hear more about that project and whats happening there Smiley

---edit---

sort of got my question awsered at 45:xx but if more details could be had i'd be very very happy Smiley especially around the talk with the accelerator guys Smiley
Regarding the CCR, someone asked a question related to this on Soma's blog: http://blogs.msdn.com/somasegar/archive/2008/06/02/june-2008-ctp-parallel-extensions-to-the-net-fx.aspx

...and Alpa Agarwal, a colleague of mine answered:
The Concurrency and Coordination Runtime (CCR) and the Task Parallel Library (TPL) are complementary technologies. TPL, which provides support for imperative data and task parallelism, is well suited for synchronous parallelism and patterns such as parallel loops. The Concurrency and Coordination Runtime is well suited for orchestrating many asynchronous components and handling asynchronous I/O in a clever manner. Though TPL and CCR may seem slightly redundant on the surface, we encourage you to try our CTP of Parallel Extensions to the .NET Framework and to provide us with feedback.