Skip to content
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

Open
j-woz opened this issue Dec 16, 2019 · 2 comments
Open

Priority threshold #182

j-woz opened this issue Dec 16, 2019 · 2 comments

Comments

@j-woz
Copy link
Contributor

j-woz commented Dec 16, 2019

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

@jozik
Copy link
Contributor

jozik commented Dec 16, 2019

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:

  • Priority threshold: defines a priority value under which tasks are accumulated until a (below defined) idle time is reached
  • Idle time: time measured from last accumulation of under priority threshold tasks, such that if tasks are not being accumulated for a while, they will be sorted by priority and sent to workers

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.

@j-woz
Copy link
Contributor Author

j-woz commented Dec 16, 2019

That makes sense.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants