Don't copy the batch when training on a single gpu #1576
Merged
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
| # Don't copy the batch since there is a single gpu that the batch could | ||
| # be referenced from and if there are multiple optimizers the batch will | ||
| # wind up copying it to the same device repeatedly. | ||
| batch = self.transfer_batch_to_gpu(batch, gpu_id) |
There was a problem hiding this comment.
what happens with multiple GPUs?
There was a problem hiding this comment.
This is in the "self.single_gpu" condition, so I don't think it's possible to have multiple gpus here? But I don't know this code very well at all.
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.
Before submitting
What does this PR do?
Fixes #1566 by removing the copy.copy(batch) when moving a batch onto the gpu. This way if there are multiple optimizers, the batch will only need to be moved to the gpu once.
PR review
Anyone in the community is free to review the PR once the tests have passed.
If we didn't discuss your PR in Github issues there's a high chance it will not be merged.
Did you have fun?
Make sure you had fun coding 🙃