Add worker_pool:dispatch_sync function
#368
Conversation
Make use of the new dispatch_sync function in rabbitmq/rabbitmq-common#368 to block only when all workers are busy
dispatch_sync sits inbetween the behavior of submit and submit_async, blocking the caller until a worker begins the task, as opposed to not blocking at all, or blocking util the task has finished. This is useful when you want to throttle submissions to the pool from a single process, such that all workers are busy, but there exists no backlog of work for the pool.
HoloRin
force-pushed
the
worker_pool_dispatch_sync
branch
from
a9e6849 to
150f8b5
Compare
I'll move that suite here, since I think next to it's implementation is a more obvious location (I looked for the suite before creating this one, but didn't find it). |
according to Michael's suggestion
to consolidate worker pool tests in a single location
|
The new tests depend on |
|
Thanks @michaelklishin |
|
@michaelklishin I need the |
Make use of the new dispatch_sync function in rabbitmq/rabbitmq-common#368 to block only when all workers are busy (cherry picked from commit 01270fd)
|
Backported to 3.8.x as part of #387. |
dispatch_syncsits in between the behavior ofsubmitandsubmit_async, blocking the caller until a worker begins the task (submitblocks until the task is scheduled and complete, whilesubmit_asyncdoes not block at all).This is useful when you want to throttle submissions to the pool from a single process, such that all workers are busy, but there exists no backlog of work for the pool.