Improved accelerator memory usage#65
Merged
Merged
Conversation
janpfeifer
commented
Aug 29, 2024
Contributor
- Immediately free accelerator (GPU) memory, where possible -- as opposed to waiting for the garbage collector.
- This impacts the train.Loop and train.Trainer: they both immediately finalize the inputs and labels after use.
- Fixed nil point exception, where initializer was not properly set if value of a variable was loaded from a checkpoint.
- This impacted when restarting training with batch normalization.
- Fixes to the notebooks: some small things were broken on the v0.11.0 transition; large speed-up with v0.11.1 fixes.
…ed to waiting for the garbage collector.
…from a checkpoint.
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
1 participant
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.