Skip to content

Add pinned_memory and non_blocking transfer for default collate_fn #52948

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

Draft
wants to merge 21 commits into
base: master
Choose a base branch
from

Conversation

srinathk10
Copy link
Contributor

Why are these changes needed?

Add pinned_memory and non_blocking transfer for default collate_fn

Related issue number

Checks

  • I've signed off every commit(by using the -s flag, i.e., git commit -s) in this PR.
  • 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 added any new APIs to the API Reference. For example, if I added a
      method in Tune, I've added it in doc/source/tune/api/ under the
      corresponding .rst file.
  • 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 :(

@srinathk10 srinathk10 changed the base branch from master to srinathk10-train-fix-collate-fn May 12, 2025 22:04
@srinathk10 srinathk10 changed the base branch from srinathk10-train-fix-collate-fn to master May 12, 2025 22:47
@srinathk10 srinathk10 marked this pull request as draft May 13, 2025 00:34
@srinathk10 srinathk10 added the go add ONLY when ready to merge, run all tests label May 13, 2025
@@ -213,6 +213,13 @@ def __call__(self, batch: "pyarrow.Table") -> Dict[str, List["torch.Tensor"]]:
# However, for CPU transfer, we need to combine the chunked arrays first
# before converting to numpy format and then to Tensors.
combine_chunks = self.device.type == "cpu"

# If the device is CPU, we don't need to pin the memory.
pin_memory = self.device.type != "cpu"
Copy link
Contributor

Choose a reason for hiding this comment

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

We should probably expose this arg to users.
pinning memory isn't always better (e.g., when there are many small batches)

Copy link
Contributor Author

Choose a reason for hiding this comment

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

yea, seeing overhead with pinning for batch size = 32

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
go add ONLY when ready to merge, run all tests
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants