Joe Duffy and Igor Ostrovsky: Parallel LINQ under the hood (Channel 9)

Joe Duffy and Igor Ostrovsky: Parallel LINQ under the hood

Posted: Mar 18, 2008 at 10:32 AM

By: Charles

(1)

19,239 Views

5 Comments

Video format

Option selected may change based on video formats available and browser capability.

Auto

Use our suggested format for this video.

Smooth Streaming

Adaptive bitrate streaming - little buffering but lower video quality at times of low bandwidth. Silverlight 5 required

Progressive

Traditional buffered video format. Silverlight 5 required

HTML5

For browsers that support H.264 MP4 or WebM video playback such as:
IE9+, Firefox 4+, Chrome 5+, or Safari 4+.

Flash

For browsers that have the Adobe Flash Player plugin installed.

Continuing our exploration of the Parallel Computing Platform and the folks who think it up and build it, we sit down with software developers Joe Duffy (he wrote the original Parallel LINQ Think Week paper that Bill Gates read and obviously enjoyed!) and Igor Ostrovsky (he spends his time implementing PLINQ and associated technologies) to deeply dig into how PLINQ works and what makes it tick from a parallel processing point of view.

Lots of whiteboarding and great conversation in this one, as is usual with the people helping to shape our general purpose parallel computing development platform.

Enjoy.

Low res file here.

Follow the Discussion

Follow
Oops, something didn't work.

Try again?

Sign In to be begin to follow these comments

What does this mean?
Following an item on Channel 9 allows you to watch for new content and comments that you are interested in. You need to be signed in to Channel 9 to use this feature.

Getting "follow" information

Stop following these comments

Start following these comments

What does this mean?
Following an item on Channel 9 allows you to watch for new content and comments that you are interested in and view them all on your notifications page.

Removing your "follow"

Setting up your "follow"

Did you know you can
sign up for email notifications?
- Subscribe to this comments

gaurav.net

Mar 18, 2008 at 10:54 AM

Awesome..
Dwnldin999....
staceyw Before C# there was darkness...

Mar 18, 2008 at 11:00 PM

Great. Thanks again Joe, Igor, and Charles.
Forcing tasks (i.e. Charles question) on many cores explicitly actually has a simple use case. Correctness debugging. If my code is tricky in terms of the delegate bodies, I may want to ensure all tasks perform on different Procs, even if the library feels 1 thread is enouph. Because your race bugs will not show up using 1 proc or even 1 thread passed around on many procs.
ymasuda_ ymasuda_

Mar 19, 2008 at 11:06 AM

Despite difficult theme of parallel algorithm computing, this talk delivered developers friendly knowledge of parallel data management. Supercomputing database language parsers and engines may have this I/O capability, and .NET languages are bound to constitute parallel processing algorithms. For developers business investment, given Parallel language and processors should have to expose extensibility points where .NET developers consider .NET Remoting and Web Services as an area of distributed computing and extensible execution stack to include parallel.

Likewise Windows kernel level thread context management, PLINQ may supply fine granular data access management for managed Threads, on the other hand Windows Clustering and Virtualization may take up supervisor on clustering nodes, and Web Farm and Data Grid may do load balancer similarly.

Development partners should be thankful for fine logical explanation of new ideas PLINQ.
littleguru <3 Seattle

Mar 19, 2008 at 2:05 PM

Thanks for this video guys!
sokhaty

Mar 23, 2008 at 9:37 AM

Good video. Too short apparently to cover the subject deep enough
General suggestion to the PLINQ team - please do provide programmers with extra knobs and switches to fine tune parallel execution flow.
Based on personal experience with SQL optimizers including the parallel ones, out of five more or less complex queries one would need a hint to run correctly.
I wouldn't expect PLINQ be any different in this regard, especially considering that it will work on data that won't have any statistics associated with them.