fix to issue #23 (CUDA out of memory at 1000th epoch) as suggested by… #74
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
…ted by 07hyx06. Surrounded print output with torch.no_grad()
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.
Fix to issue #23 (CUDA out of memory at 1000th epoch) as suggested by @07hyx06. Surrounded print output with torch.no_grad().
Tested by running on an internal large dataset. Before the fix, it stopped at 1000th epoch, complaining that it was out of memory. After fix, it's still running at 128,000 epochs. Memory initially 22157MB on GPU, and has not increased during training.