-
Notifications
You must be signed in to change notification settings - Fork 22
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
Priority threshold #182
Comments
My sense is that the queue length won't help in the use cases we were thinking about, but a combination of the following two:
would. Without the priority threshold value (i.e., one that says what's the threshold of priority values for tasks under which they will be accumulated), we'd be tracking tasks that don't need to be accounted for, so it would be particularly hard to assign a meaningful queue length. Also, our use cases indicated that providing a task accumulation idle time should be simple and intuitive enough to specify. |
That makes sense. |
Need a feature to suspend release of prioritized tasks until a user-provided queue size (or time) is reached, allowing for prioritization to happen.
Start with TURBINE_PRIORITY_THRESHOLD=10
meaning: don't release prioritized tasks until 10 are in the queue.
CC @jozik @ncollier
The text was updated successfully, but these errors were encountered: