Replies: 1 comment 1 reply
-
Hi @haines, we've made a big step forward in addressing some of these use cases with the new concurrency limits feature in River Pro. It would let you limit any given customer's concurrency on a particular queue or queue + job type, though it doesn't allow bursting to take advantage of unused worker slots. I hope you still find it useful! |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
This is somewhat related to #551 and #626.
We have a multi-tenanted platform where we don't want jobs being run for a very busy tenant to starve other tenants of workers, but at the same time we want to make use of all the worker capacity available.
Is there a sensible way to achieve this with River as-is, or is that a feature that could be considered in future?
Beta Was this translation helpful? Give feedback.
All reactions