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

Binpacking support for DoEKS #614

Open
hitsub2 opened this issue Aug 19, 2024 · 1 comment
Open

Binpacking support for DoEKS #614

hitsub2 opened this issue Aug 19, 2024 · 1 comment
Labels

Comments

@hitsub2
Copy link
Contributor

hitsub2 commented Aug 19, 2024

Community Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment

What is the outcome that you are trying to reach?

For running batch jobs, like Spark workloads, we want to have higer resource utilization and cost efficiency to avoid spreading pods across nodes leading nodes can be scaled-in in time.

By default, the scheduling-plugin NodeResourcesFit use the LeastAllocated for score strategies. For the long running workloads, that is good because of high availability. But for batch jobs, like Spark workloads, this would have high cost. By changing the from LeastAllocated to MostAllocated, it avoids spreading pods across all running nodes, leading to higher resource utilization and better cost efficiency.

Describe the solution you would like

Support binpacking strategy.

Describe alternatives you have considered

Using the custom scheduler like Yunikorn or Volcano. But it is complicated in some scenarios that we only need the binpacking.

Additional context

Copy link
Contributor

This issue has been automatically marked as stale because it has been open 30 days
with no activity. Remove stale label or comment or this issue will be closed in 10 days

@github-actions github-actions bot added the stale label Sep 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant