-
Notifications
You must be signed in to change notification settings - Fork 31k
🚨 Implement gradient checkpointing in GPTBigCode #41818
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
Open
githubnemo
wants to merge
7
commits into
huggingface:main
Choose a base branch
from
githubnemo:issue/gpt-bigcode-gradient-checkpointing
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+132
−115
Open
Changes from all commits
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
b358bf5
Implement gradient checkpointing in GPTBigCode
09eeb4d
Improve gradient checkpointing tests
4e09628
Remove duplicated gradient checkpointing code
ccf4b92
Address review comments
2db4fc5
Make test output consistent
68eef7f
GradientCheckpointingLayer for xlstm, zamba, zamba2
55a09f0
GradientCheckpointingLayer for swiftformer
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
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.
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.
Let's not change the order here, we could break things for users here. Rather change the args, kwargs positions if necessary on the module call
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.
I'm not sure that this is possible. It is mandatory that we pass
layer_pastas keyword argument, otherwiseGradientCheckpointingLayerwill not be able to remove it from the kwargs in case of gradient checkpointing. On the other hand every input that may require gradients (hidden_states,encoder_hidden_states) must be passed as positional argument forcheckpoint()to work. Maybe I'm missing something but I don't think we can bring those together without movingencoder_hidden_statesup in the list.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.
I mean that the signature should stay the same, e.g. see
transformers/src/transformers/models/gpt_bigcode/modeling_gpt_bigcode.py
Lines 586 to 596 in 84d19be
It will need to adjust the calls from the module above like
transformers/src/transformers/models/gpt_bigcode/modeling_gpt_bigcode.py
Lines 901 to 910 in 84d19be
Changing the signature is breaking a bit too much!
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 viz, as discussed internally, we need this to be breaking