farmerjoe12 / cppthreadpool Goto Github PK

At this point in the project, I am under the impression that an effective thread pool needs to have some sort of job manager. This could be implemented as a priority queue which holds onto jobs who will be delegated out to the threads for execution. I am unsure if priority queues should manage themselves and their loading and offloading, or if a separate task manager entity should be implemented in order to efficiently handle job delegation.

A thread pool is probably some type of list-esque data structure which serves to store a number of Thread objects. The "thread pool" is the purpose of this repository, but jobification and multi-core task distribution extends beyond the realm of data structures for Thread objects.

As I see it, the beginning of a thread pool starts with a query to the host machine for the number of available "threads" that can be utilized. So, the first issue here is to query any platform of execution, recieve the number of threads, then create thread "objects" to effectively maximize the distribution of a workload.

These threads should maintain their own "operation status" which can be thought of and used as a "busy indicator". If a thread is busy, find another thread to give a job to.