Decentralized Task Scheduling Techniques in .NET
I have been trying to learn more details on CLR 4.0. and the ThreadPool
and the different strategies that Microsoft recommended. I consider myself
fairly up-to-date on a lot of these topics, and use threading and
concurrent code on a daily basis.
I have been goign back through the Parallel Patterns and Practices again
recently, and am a bit caught on the Decentralized Scheduling Techniques
section which gives a brief overview of 'Work Stealing' and local vs
global thread queues.
The questions I have are:
1) Is work stealing opt-in or opt-out? Same for using local thread queues?
Or does this happen by default with CLR 4.0?
2) Do we have control over whether we are using local or global thread
queues? If so, through what API calls?
No comments:
Post a Comment