You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When resizing the reusable_executor, the call_queue is not resized.
It has a size 2 * n_workers + 1 originally so if the executor is enlarged a lot, this can cause sub-optimal performances as some workers might starve.
We might want to consider if we can resize the call_queue (probably hard as the size is defined with a BoundedSemaphore and it is hard to change it in all workers) or find an heuristic that works well.
The text was updated successfully, but these errors were encountered:
When resizing the
reusable_executor
, thecall_queue
is not resized.It has a size
2 * n_workers + 1
originally so if the executor is enlarged a lot, this can cause sub-optimal performances as some workers might starve.We might want to consider if we can resize the
call_queue
(probably hard as the size is defined with aBoundedSemaphore
and it is hard to change it in all workers) or find an heuristic that works well.The text was updated successfully, but these errors were encountered: