Repository navigation
fix(train): resume at exact global step instead of flooring to grad-accum boundary #43
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
longzhenren
wants to merge
4
commits into
OpenWAM-Official:main
Choose a base branch
from
longzhenren:fix/resume-exact-step
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
6a28e7c
fix(train): resume at exact global step instead of flooring to grad-a…
longzhenren 05206b9
fix(train): degrade mid-cycle resume to the last sync boundary
longzhenren 099c0f0
fix(train): reject mid-cycle checkpoints on resume
longzhenren 099af40
fix(train): write resumable states only at sync boundaries and skip u…
longzhenren File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[P2] Carry the save request to the next synchronization boundary
The full-state write is still nested under
global_step % save_steps == 0. When a scheduled save is mid-cycle, this branch logs that it is deferred but records no pending request; the next sync boundary never enters the branch. Only an intersection of the save interval and synchronization schedule can produce a resumable checkpoint.I reproduced this with the actual trainer loop,
save_full_states_for_resume=true, 1001 batches/epoch, accumulation=4, the defaultsave_steps=2000, and 5 epochs. Steps 2000 and 4000 were skipped; real sync boundaries 2001 and 4003 did not save either. Interrupting at step 4500 left onlycheckpoint_step_4000.safetensorsand noaccel_state_step_*directory. The run therefore cannot resume despite two scheduled saves.Please retain a pending full-state-save request and service it at the next actual synchronization boundary, even when that step is not divisible by
save_steps. A smaller regression case is 100 batches/epoch, accumulation=4, save interval=3: the request at 3 should create a resumable state at 4.