Hey all,
I was wondering if anyone had already used the new(er) ThreadPool API for win32 from MASM?
It's not present by default in the includes, but I know most of the C++ apps that are going multi-core or customer task schedulers are using this API. To be honest though if you follow the design for a task-stealing scheduler, I'm not sure if this API would really offer any benefit, as the whole point is that you don't have to create threads but rather have a (n-1) additional task threads (IE: one per core) which are blocking on a semaphore until they're assigned a task.
i think that's a .NET class - not an API :P
haven't seen too much .NET stuff in here
Umm.. no it's a replacement of the original thread pool api, the new one was introduce for Vista/Server2008 and up.
ms-help://MS.W7SDK.1033/MS.W7SDKCOM.1033/dllproc/base/thread_pool_api.htm
Link to the base page straight from Platform SDK.
my bad
i haven't gotten to win7, yet
as always, i am behind - still trying to learn xp :P
FWIW, an MSDN Magazine article about it. I've never used them.
Improve Scalability With New Thread Pool APIs (http://msdn.microsoft.com/en-us/magazine/cc163327.aspx)
I read about it but not used it myself. It's interesting, but I can't see from the article how this helps prioritize one pool over another (in other words, one group of threads over an another as the article alludes is beneficial in some situations - just seems like additional overhead)?
It also seems to me that the optimum number of thread pools is at least (processor count / 2) if not less, otherwise if you have an equal number of pools to processors, the threads in each pool start to choke on processor availability?
I eventually landed up not bothering with the new api's. From my tests the approach I landed up taking seems to be working the best.
That is to use the traditional thread functions and have a "mini scheduler".
I create a thread per core, the scheduler then resumes/suspends them and essentially assigns in function pointers.
It allows me to assign tasks/jobs liberally to specific cores without any thread overhead and works beautifully for fine-grained parallel algorithms.
Nice!!