Entries:
Comments:
Posts:

Loading User Information from Channel 9

Something went wrong getting user information from Channel 9

Latest Achievement:

Loading User Information from MSDN

Something went wrong getting user information from MSDN

Visual Studio Achievements

Latest Achievement:

Loading Visual Studio Achievements

Something went wrong getting the Visual Studio Achievements

Joe Duffy and Igor Ostrovsky: Parallel LINQ under the hood

Download

Right click “Save as…”

  • Mid Quality WMV (Lo-band, Mobile)
  • MP3 (Audio only)
  • MP4 (iPhone, Android)
  • High Quality MP4 (iPad, PC, Xbox)
  • Mid Quality MP4 (Windows Phone, HTML5, iPhone)
  • WMV (WMV Video)
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.

Tags:

Follow the Discussion

  • Awesome..
    Dwnldin999....
  • William Staceystaceyw Before C# there was darkness...
    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.
  • Yoshihiro Masudaymasuda_ ymasuda_

    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.

  • Christian Liensbergerlittleguru <3 Seattle
    Thanks for this video guys! Smiley
  • Good video. Too short apparently to cover the subject deep enough Smiley
    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.

Remove this comment

Remove this thread

close

Comments Closed

Comments have been closed since this content was published more than 30 days ago, but if you'd like to continue the conversation, please create a new thread in our Forums,
or Contact Us and let us know.