Overview
Examples
Screenshots
Comparisons
Applications
Download
Documentation
Tutorials
Bazaar
Status & Roadmap
FAQ
Authors & License
Forums
Funding Ultimate++
Search on this site
Search in forums












SourceForge.net Logo
Home » U++ Library support » U++ MT-multithreading and servers » what about WorkQueue : public CoWork
Re: changed CoWork and derived WorkQueue [message #24907 is a reply to message #24901] Wed, 03 February 2010 20:45 Go to previous messageGo to previous message
mirek is currently offline  mirek
Messages: 14267
Registered: November 2005
Ultimate Member
kohait00 wrote on Wed, 03 February 2010 09:14

thus an app is able to specify maybe "Workgroups". say following case:

task A, B, C each depends on each other, cause they might use same ressources, so best execute them in one thread somewhere else else than main thread, task C, D, E, are again each dependant on each other but *NOT* dependant on A, B, C, so they get their own WorkQueue (and Thread), and so are able to be executed sequentially related to each other, but parallelly related to other independant groups.. sounds complicated, right? hope it still makes sense

using the same static pool would mean using a bunch of threads, so supplied work to WorkQueue again gets executed parallely, but not sequentially (=>queue). in that case one could stick to CoWork usage, there is no difference then


Note that the static pool only limits the number of threads running in parellel at any single time - which is a good thing, as you also have limited number of cores... I would say it has little to do with dependency of tasks.
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: DnD hangs in MT Refresh()ing
Next Topic: Linux MT problems with time functions
Goto Forum:
  


Current Time: Thu Aug 28 15:50:07 CEST 2025

Total time taken to generate the page: 0.06488 seconds