Repository navigation
Release unused CLI checkpoint payload before training - #59
Merged
Merged
Conversation
2 of 5 tasks
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.
Change
Refs #3.
Release the CLI checkpoint dictionary before entering train. The model and tokenizer remain owned by training; the initialization parent digest is saved separately, and resume still supplies no initialization parent. This avoids retaining unused deserialized weights and optimizer tensors while the trainer loads resume state again.
Four weak-reference regressions cover train/reward-train and init/resume. They assert payload collection, two-step configuration and unchanged lineage/resume arguments. Earlier source fails all four; the fix passes all four. This establishes object ownership; actual full-checkpoint RSS savings and native full-weight feasibility remain unmeasured.
Validation
No optimizer math, configuration identity, telemetry or API shape changes.