Repository navigation
Conversation
Write the scaled product to optimizer storage so a second load observes the original FP32 moments and master weights. Keep scalar states scalar. Signed-off-by: ZenAlexa <zimingwang945@gmail.com>
This branch has not been deployed
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
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.
Description
Loading an FP32 optimizer checkpoint into FP16 states scales the checkpoint tensors in place. A second load then treats those already scaled values as unscaled moments or master weights, so training resumes with different optimizer state.
Write the scaled FP32 product directly to its FP16 destination. Keep the per-tensor scale scalar so loading a zero-dimensional parameter preserves its shape. The checkpoint format and optimizer API stay unchanged.
Verification
a7aec214; the change is in the PyTorch optimizer.