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

Scope weighting for compute service #241

Open
mikemhenry opened this issue Feb 14, 2024 · 0 comments
Open

Scope weighting for compute service #241

mikemhenry opened this issue Feb 14, 2024 · 0 comments

Comments

@mikemhenry
Copy link
Collaborator

In broad terms, what are you trying to do?

A compute service operator should be able to weight different compute scopes to control the allocation of compute effort.

Briefly detail what you have already tried

Describe the new feature(s) that would help you to achieve this

I think two different methods would be nice to support for weighting different scopes.
One method would be weights, so like:

scopes: (mhenry-*-*, 0.1), (openfe-*-*, 0.1), (asap-*-* 0.2), (choderalab-*-*, 0.1), (asap-confidential-*, 0.5)

That would mean the compute worker would get a asap-confidential-* job 50% of the time, and a openfe-*-* job 10% of the time.

Another method that would be good to support is a simple rank order priority:

scopes: (mhenry-*-*, 5), (openfe-*-*, 4), (asap-*-* 2), (choderalab-*-*, 3), (asap-confidential-*, 1)

Where the compute service will only grab asap-*-* jobs if there are 0 asap-confidential-* jobs in the queue.

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

No branches or pull requests

2 participants