How it works...
ThreadPool is made of two major components: a bunch of threads and a bunch of queues. When the pool is created, a few orchestration threads are started together with as many worker threads as you specified at pool initialization.
The worker threads will be in charge of actually running the tasks you dispatch to them, while the orchestration threads will be in charge of managing the worker threads, doing things such as telling them to quit when the pool is closed, or restarting them when they crash.
If no number of worker threads is provided, TaskPool will just start as many threads as the amount of cores on your system as returned by os.cpu_count().
Once the threads are started, they will just sit there waiting to consume ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access