Custom step batch size rampup schedules#3779
Open
mkhona-nvidia wants to merge 5 commits intoNVIDIA:mainfrom
Open
Custom step batch size rampup schedules#3779mkhona-nvidia wants to merge 5 commits intoNVIDIA:mainfrom
mkhona-nvidia wants to merge 5 commits intoNVIDIA:mainfrom
Conversation
Remove upfront divisibility validation from _validate_schedule() so that early schedule entries smaller than micro_batch_size * data_parallel_size (e.g., after scaling to more GPUs mid-training) no longer crash at init. Divisibility of the current batch size is still checked in update() when consistency_check=True, which runs after checkpoint loading. Also fix stale test signatures for init/reconfigure_num_microbatches_calculator. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
…eckpoint load Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Tests cover: - Step schedule consistency check fails when batch < micro_batch_size * dp_size - Step schedule with decrease_batch_size_if_needed rounds to 0 microbatches - Rampup consistency check fails when batch too small for world size Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Contributor
|
This PR has been automatically converted to draft because all PRs must start as drafts. When you are ready for review, click Ready for Review to begin the review process. This will:
See the contribution guide for more details. |
svcnvidia-nemo-ci
added
Final Review
mkhona-nvidia
changed the title
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
2 participants
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.
What does this PR do ?
This PR builds custom batch size schedules instead of relying on megatron's automatic, constant increment rampup.
Contribution process
Pre-checks
Code review
Feel free to message or comment the @mcore-oncall to help accelerate your merge into main. The less complex your PR is, the faster it will be approved and merged!
All PRs start as draft. If you open a non-draft PR, it will be automatically converted to draft.
Step 1: Mark PR as "Ready for Review"
.github/CODEOWNERS.Final Review might get declined if these requirements are not fulfilled.
Step 2: Final Review
For PRs that change
megatron/core, once all expert reviewers have approved, theFinal Reviewlabel is applied automatically and final reviewers are assigned.For PRs outside
megatron/core, this step is skipped.Step 3: Approved
Once all required reviewers have approved, the
Approvedlabel is applied automatically.Merge
Any member of mcore-engineers will be able to merge your PR.
For MRs into `dev` branch
The proposed review process for `dev` branch is under active discussion.MRs are mergable after one approval by either
eharper@nvidia.comorzijiey@nvidia.com.