-
-
Notifications
You must be signed in to change notification settings - Fork 176
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
Use pubsub and blocking for improved response times #404
Comments
CC @arturzx |
See also how |
A draft PR welcome.😊 |
My plan is to move to redis streams which are by far the best solution for tasks like those performed by arq. Stay tuned for a big update. |
See #437. |
I agree that redis stream is the best option right now. Can't wait for the arq update, I developed a redis stream based library, aka brq. If you're in a hurry, you may try it now. |
arq currently uses a polling mode (default 0.5 seconds) to fetch jobs on worker side and also to fetch results.
I think it should be possible to use blocking requests (on worker side) and pubsub (possibly with keyspace notifications, but not necessarily) for fetching the result.
This should be quite reliable in most scenarios, however it can occur that a job gets lost (there is no guarantee for pubsub delivery after all), so one could still poll from time to time to be on the safe side.
Are there any opinions on development in this direction?
From #374 (comment)
The text was updated successfully, but these errors were encountered: