Change constant torch.tensor to torch.full#20061
Merged
sgugger merged 1 commit intohuggingface:mainfrom Nov 4, 2022
Merged
Conversation
|
The documentation is not available anymore as the PR was closed or merged. |
sgugger
approved these changes
Nov 4, 2022
Collaborator
sgugger
left a comment
There was a problem hiding this comment.
LGTM, thanks for your PR!
@michaelbenayoun would this cause any issue for our torch FX/ONNX conversions?
Member
|
For FX, I think this is already tested in the CI so I guess it does not break things. |
Contributor
|
Following the change, the training with ONNX Runtime breaks as |
This was referenced Dec 7, 2022
Closed
mpierrau
pushed a commit
to mpierrau/transformers
that referenced
this pull request
Dec 15, 2022
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
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.
What does this PR do?
Change
torch.tensortotorch.fullfrom GPT-2 to avoid CPU-GPU synchronization.Benchmarks with PyTorch Profiler
Here's a trace of a single GPT-2 training iteration with 12 GPT-2 blocks, 2 GPUs, and DDP.
From
_attnfunction, there are twotorch.tensorcalls. Those invoke CPU to GPU memory movement, thus callingcudaStreamSynchronize.How to fix
From PyTorch Recipes, we can avoid CPU-GPU synchronization by directly calling
torch.fullinstead oftorch.tensorortorch.to. Since twotorch.tensorcreate constant tensors, we can change those intotorch.full([], ...), and it will behave the same way.After the patch, every
cudaStreamSynchronizeis gone, and the duration of a single iteration is reduced by 0.5%.Fixes # (issue)
Before submitting
Pull Request section?
to it if that's the case.
documentation guidelines, and
here are tips on formatting docstrings.
Who can review?
Anyone in the community is free to review the PR once the tests have passed. Feel free to tag
members/contributors who may be interested in your PR.
@LysandreJik