Avoid busy loop in workers, while waiting for work. #214
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
My application has a main loop that basically looks like
The last part is listening for postgresql notifications when database tables change, and then calling
queue_work()
. One minor issue is that the worker processes are in fact doing busy looping (with a small 0.005s delay) while callingget_no_wait
on the queue repeatedly. On the other hand, if the worker is not handling any pending work, we might as well call a blockingget
while waiting for initial work.