TaskCompletionSource
Description
Join Danny Shih as he demonstrates using the range partitioner feature. Parallel.For is great, but being a general solution, it does not perform optimally for certain specific scenarios, such as when there are a ton of iterations and very little work per iteration. In these cases, the range partitioner can be used to speed things up.
Learn more about the .NET Framework 4 and keep abreast of Parallel Computing tools and techniques via the Concurrency Dev Center.
See all videos in this series.
Share
Download
Download this episode
- Mid Quality WMV (17.6 MB)
- MP3 (3.9 MB)
- Low Quality MP4 (13.5 MB)
More episodes in this series
Windows PowerShell : A Brief Introduction to using WPF Containers in WPK
Related episodes
TaskCompletionSource
Task and Task<TResult>, Waiting and Continuations
Refactoring "for" Loops to Run in Parallel
Concurrent Programming with .NET4 Collections
How to Cancel Work using .NET4 CancellationToken
The .NET4 Countdown Synchronization Primitive
Lazy<T> Optimized Resource Initialization
Concurrent Visualization Techniques in the VS2010 Profiler
BlockingCollection<T> Demonstration in Producer-Consumer Scenarios
Thread Blocking Analysis in the VS2010 Profiler
The Discussion
-
macias Nice video, thank you -- one wish though, please do the recording when you are in good shape (no cold).
-
bangoker Cool, I've had to do the manual partitioning of structures before, and yeah its tidious... great addition! (I hope you get better!)
Comments closed
Comments have been closed since this content was published more than 30 days ago, but if you'd like to send us feedback you can Contact Us.