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
[Feature Request] Worker Rate Limit without Duration #909
Comments
Ok, so more like a global concurrency parameter instead of the current per worker concurrency right? |
Yup! |
Note for future implementer: the challenge here is not so much limiting the amount of active jobs at any given time, but how to "wake" the workers that will be sleeping while the limit has been reached. We want the workers to wake up as soon as they are needed and in a robust way so that they "always" start working as soon as the active number goes below the threshold. Events could be used but the biggest drawback is that events will be sent to all sleeping workers, if there is a large pool of workers this will imply that the workers will all try to start processing new jobs but maybe only a handful will succeed, creating unnecessary stress on Redis. |
A global concurrency feature would be useful for me as well |
+1 on this one, super useful if implemented. |
+1 on this. I agree this would be extremely useful |
Closing this issue as this has been already implemented for a while: https://docs.bullmq.io/bullmq-pro/groups/concurrency |
It would be nice to be able to rate limit without a duration for a group
For example:
A job that downloads something from a remote machine as fast as possible but only have 5 concurrent downloads available.
Currently we are using redis to keep track of the number of jobs currently running and then delay them if there's 5 already running.
Im sure theres a better way , and open to ideas
The text was updated successfully, but these errors were encountered: