Repository navigation
Enable OOC KMeans transfer/compute overlap for pageable input #2851
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
rapids-bot
merged 12 commits into
NVIDIA:main
from
viclafargue:ooc-kmeans-pageable-overlap
Oct 30, 2026
Merged
Changes from all commits
Commits
Show all changes
12 commits
Select commit
Hold shift + click to select a range
eed641d
Enable OOC KMeans transfer/compute overlap for pageable input
viclafargue ac3b8db
Merge branch 'main' into ooc-kmeans-pageable-overlap
viclafargue 890ba9d
Addressing review
viclafargue 40bbece
raft::resource::sync_stream
viclafargue 997939b
Merge branch 'main' into ooc-kmeans-pageable-overlap
viclafargue 1786f22
Merge branch 'main' into ooc-kmeans-pageable-overlap
viclafargue 522c0cc
Skip pinned staging for single-batch k-means input
viclafargue 2a12a92
Merge branch 'main' into ooc-kmeans-pageable-overlap
viclafargue 07dd66f
Revert "Skip pinned staging for single-batch k-means input"
viclafargue a152393
Merge branch 'main' into ooc-kmeans-pageable-overlap
viclafargue 8d10cec
Merge branch 'main' into ooc-kmeans-pageable-overlap
viclafargue c19db8c
Merge branch 'main' into ooc-kmeans-pageable-overlap
viclafargue File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One minor concern: for the single batch case (device_buffer_samples = 0), we are doing the additional copy to a pinned buffer. Do you think it would be beneficial to directly transfer to device in that case (so if number of batches == 1, skip the kmeans batch loader entirely)?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For a single batch, the transfer happens only once, so it mostly comes down to the cost of explicitly allocating and filling a pinned buffer versus the time cudaMemcpyAsync may block while staging internally. I'm not sure the change is worth it. I'd also keep the batch loader responsible for managing the data, since bypassing it for the single-batch case would add complexity.