Changed CheckpointManager to write the latest checkpoint to a consistent filename #2123
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.
This changes the checkpoint format from encoding the global step in the filename to having a single
latest.ckpt
file.The previous approach required having a background process that would cleanup old checkpoints as training progressed. However, since we only retain the latest checkpoint, this added extra overhead for no benefit, and also caused synchronization issues when background processes would attempt to copy checkpoint files while they were being deleted by the training process.
In this implementation, the global step is instead put into the state dict along with model and optimizer weights. Additionally, checkpoints are first written to a temp directory to guarantee atomicity and prevent background processes from syncing tempfiles that will later be deleted.