8000 [Core] Support max cpu allocation per node for placement group scheduling by rkooo567 · Pull Request #26397 · ray-project/ray · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

[Core] Support max cpu allocation per node for placement group scheduling #26397

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

Merged

Conversation

rkooo567
Copy link
Contributor
@rkooo567 rkooo567 commented Jul 8, 2022

Why are these changes needed?

The PR adds a new experimental flag to the placement group API to avoid placement group taking all cpus on each node. It is used internally by Air to avoid placement group (created by Tune) is using all CPU resources which are needed for dataset

Related issue number

Checks

  • I've run scripts/format.sh to lint the changes in this PR.
  • I've included any doc changes needed for https://docs.ray.io/en/master/.
  • I've made sure the tests are passing. Note that there might be a few flaky tests, see the recent failures at https://flakey-tests.ray.io/
  • Testing Strategy
    • Unit tests
    • Release tests
    • This PR is not tested :(

@rkooo567
Copy link
Contributor Author
rkooo567 commented Jul 8, 2022

cc @matthewdeng I fixed the bugs and am waiting for the test result. If the test result seems good, I will ping you (you can start experimenting it or ping me to pair experimenting if you;d like to)

@scv119 scv119 self-assigned this Jul 11, 2022
@scv119
Copy link
Contributor
scv119 commented Jul 11, 2022

let's update the title and summary.

@scv119 scv119 added the @author-action-required The PR author is responsible for the next step. Remove tag to send back to the reviewer. label Jul 11, 2022
@rkooo567 rkooo567 changed the title [WIP] Core/feat/placement group max cpu frac [Core] Support max cpu allocation per node for placement group scheduling Jul 15, 2022
@ericl ericl self-assigned this Jul 15, 2022
Copy link
Contributor
@scv119 scv119 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@rkooo567 rkooo567 added the do-not-merge Do not merge this PR! label Jul 16, 2022
@rkooo567
Copy link
Contributor Author

ADdressed @scv119 ' comments, but I haven't pushed yet (finalizing unit tests).

@rkooo567
Copy link
Contributor Author

I will merge it after pushing the code

@rkooo567 rkooo567 removed the do-not-merge Do not merge this PR! label Jul 16, 2022
@rkooo567 rkooo567 merged commit 0f01026 into ray-project:master Jul 16, 2022
xwjiang2010 pushed a commit to xwjiang2010/ray that referenced this pull request Jul 19, 2022
…ling (ray-project#26397)

The PR adds a new experimental flag to the placement group API to avoid placement group taking all cpus on each node. It is used internally by Air to avoid placement group (created by Tune) is using all CPU resources which are needed for dataset

Signed-off-by: Xiaowei Jiang <xwjiang2010@gmail.com>
Stefan-1313 pushed a commit to Stefan-1313/ray_mod that referenced this pull request Aug 18, 2022
…ling (ray-project#26397)

The PR adds a new experimental flag to the placement group API to avoid placement group taking all cpus on each node. It is used internally by Air to avoid placement group (created by Tune) is using all CPU resources which are needed for dataset

Signed-off-by: Stefan van der Kleij <s.vanderkleij@viroteq.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
@author-action-required The PR author is responsible for the next step. Remove tag to send back to the reviewer.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants
0