[core] Remove experimental max_cpu_frac_per_node
#53610
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@stephanie-wang you have the most context on this one, could you take a look? |
|
@matthewdeng is also working on confirming it's unused |
matthewdeng
approved these changes
Jun 6, 2025
…es/rm-cpu-max-frac
…es/rm-cpu-max-frac
max_cpu_frac_per_nodemax_cpu_frac_per_node
|
We should be good to remove, but I'm going to do a deprecation warning for at least one release before killing it |
|
This pull request has been automatically marked as stale because it has not had You can always ask for help on our discussion forum or Ray's public slack channel. If you'd like to keep this open, just leave any comment, and the stale label will be removed. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Introduced for Ray AIR, no longer used by any Ray libraries, but never finished (does not work with autoscaler).
This is exposed in the public
ray.util.placement_groupAPI, but it is marked experimental with a strong caveat and we aren't aware of any external usage, so going to directly remove it.