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

Autoscaling of different WorkerGroups #933

Open
ghalter opened this issue Feb 21, 2025 · 1 comment
Open

Autoscaling of different WorkerGroups #933

ghalter opened this issue Feb 21, 2025 · 1 comment

Comments

@ghalter
Copy link

ghalter commented Feb 21, 2025

Hi,

I was wondering if there is any plans for allowing to define autoscalers per worker group, I think this could be quite a useful feature.

E.g. in our case we have two groups, "low-mem" which is the default group and "high-mem", the service picks the workers based on guessed workload. Small tasks go to low-mem, big tasks go to high-mem.
We then have an autoscaler, but as the docs states, only the default group is auto scaled.

Our current solution is to have to clusters and pick between the two, but maybe I'm missing something?

Cheers

@jacobtomlinson
Copy link
Member

I would love to see this feautre make its way in, but we would need to make a bunch of scheduler changes in dask/distributed to make that happen. If folks are motivated to work on this then I would be happy to review PRs and walk them through the process.

the service picks the workers based on guessed workload

I think this is the biggest challenge. How do we know which group to scale. We have previously explored using resource annotations to do this, but nothing came of it.

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