-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
flow.async: In ..._task_loop, add a way to get number of pending jobs in the thread pool job queue. #62
Comments
I did not file the original ticket in pre-open-source days but added this comment back then: That's actually quite a topic I have been thinking about, which is referenced in , regarding better balancing in Segregated_thread_task_loop (note: Cross_... uses boost.asio which balances it itself) and in the optional per_thread_ops() feature of the Concurrent_task_loop hierarchy. The job queue size is helpful for that and other things. It's quite a topic. I'll need to think a lot about this; it's complicated. -- The link talks about the following Host_resolver class being used elsewhere. For context including it here: ---snip--- Currently Host_resolver starts a manually configured # of threads (a quite conservative high number, 500 default). That's fine - no reason to think it's insufficient (although there may be overhead in so many threads, not something we're deeply worried about, but it's out there). It would be better to automatically start threads as needed. Minimally:
---end-snip--- Revisit this with original reporter (Arun Poruri), in case there are more thoughts nowadays. |
In flow::async::*_task_loop, add a way to get number of pending jobs in the thread pool job queue.
The text was updated successfully, but these errors were encountered: