[Data] Make chunk combination threshold configurable for improved per… #51200
Conversation
This file contains 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
…formance flexibility The decision to combine chunks is based on a threshold for the number of chunks, set by MIN_NUM_CHUNKS_TO_TRIGGER_COMBINE_CHUNKS. To make this more flexible, we have made this threshold configurable via the RAY_DATA_MIN_NUM_CHUNKS_TO_TRIGGER_COMBINE_CHUNKS environment variable. This configurability is important because the size of each chunk can vary greatly depending on the dataset and the operations performed previously. A fixed threshold might not be optimal for all scenarios, as in some cases, a smaller number of large chunks could behave differently from a larger number of smaller chunks. By making this threshold tunable, users have the ability to optimize for their specific case, adjusting based on their chunk sizes and available memory. Signed-off-by: ShaochenYu-YW <[email protected]>
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.
Why are these changes needed?
The decision to combine chunks is based on a threshold for the number of chunks, set by MIN_NUM_CHUNKS_TO_TRIGGER_COMBINE_CHUNKS. To make this more flexible, we have made this threshold configurable via the RAY_DATA_MIN_NUM_CHUNKS_TO_TRIGGER_COMBINE_CHUNKS environment variable. This configurability is important because the size of each chunk can vary greatly depending on the dataset and the operations performed previously. A fixed threshold might not be optimal for all scenarios, as in some cases, a smaller number of large chunks could behave differently from a larger number of smaller chunks. By making this threshold tunable, users have the ability to optimize for their specific case, adjusting based on their chunk sizes and available memory.
made this threshold configurable via the RAY_DATA_MIN_NUM_CHUNKS_TO_TRIGGER_COMBINE_CHUNKS environment variable.
Related issue number
N/A, I can create one if needed
Checks
git commit -s) in this PR.scripts/format.shto lint the changes in this PR.method in Tune, I've added it in
doc/source/tune/api/under thecorresponding
.rstfile.