This question may be subjective but i just want to know when to use TPL and when to use native thread based synchronization (evnts, wait handles).
Will the native thread synchronization techniques be obsolete going forward?
Thanks
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
This question may be subjective but i just want to know when to use TPL and when to use native thread based synchronization (evnts, wait handles).
Will the native thread synchronization techniques be obsolete going forward?
Thanks
Use TPL wherever you can because it’s a cleaner, more declarative way to express your needs for parallelism.
MSDN explains “The TPL scales the degree of concurrency dynamically to most efficiently use all the processors that are available. In addition, the TPL handles the partitioning of the work, the scheduling of threads on the ThreadPool, cancellation support, state management, and other low-level details. By using TPL, you can maximize the performance of your code while focusing on the work that your program is designed to accomplish.”
See also http://www.albahari.com/threading/part5.aspx which details the benefits of ‘Data Parallelism’ and other TPL benefits.