Fix not evaluating the optimizer state after each step#381
Open
waldheinz wants to merge 1 commit intofilipstrand:mainfrom
Open
Fix not evaluating the optimizer state after each step#381waldheinz wants to merge 1 commit intofilipstrand:mainfrom
waldheinz wants to merge 1 commit intofilipstrand:mainfrom
Conversation
Not doing this causes huge memory use if neither "should_plot_loss", "should_generate_image" or "should_save" force an evaluation in the code below.
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.
Not doing this causes huge memory use if neither "should_plot_loss", "should_generate_image" or "should_save" force an evaluation in the code below.
I found this when setting
plot_frequencyto 32 because evaluating the loss using the validation set is not cheap at all. But this is a separate issue.