Implementation of a more flexible optimizer/scheduler override system - #2723
Merged
Conversation
Signed-off-by: John St John <jstjohn@nvidia.com>
jstjohn
commented
Dec 19, 2025
… (no longer 1-1 constraint) Signed-off-by: John St John <jstjohn@nvidia.com>
Signed-off-by: John St John <jstjohn@nvidia.com>
Signed-off-by: John St John <jstjohn@nvidia.com>
Signed-off-by: John St John <jstjohn@nvidia.com>
… but False Signed-off-by: John St John <jstjohn@nvidia.com>
jstjohn
commented
Dec 19, 2025
Signed-off-by: John St John <jstjohn@nvidia.com>
jstjohn
commented
Dec 19, 2025
Signed-off-by: John St John <jstjohn@nvidia.com>
Signed-off-by: John St John <jstjohn@nvidia.com>
… for the user to make use of Signed-off-by: John St John <jstjohn@nvidia.com>
Signed-off-by: John St John <jstjohn@nvidia.com>
Contributor
|
/ok to test 6ae2c41 |
Signed-off-by: John St. John <jstjohn@nvidia.com>
Contributor
|
/ok to test 7d1ecc3 |
Contributor
Author
|
/ok to test ac4470e |
jstjohn
enabled auto-merge
January 6, 2026 20:01
github-merge-queue
Bot
removed this pull request from the merge queue due to failed status checks
Jan 6, 2026
BoxiangW
pushed a commit
to BoxiangW/Megatron-LM
that referenced
this pull request
Jan 9, 2026
…NVIDIA#2723) Signed-off-by: John St John <jstjohn@nvidia.com> Signed-off-by: John St. John <jstjohn@nvidia.com>
maanug-nv
pushed a commit
to maanug-nv/Megatron-LM
that referenced
this pull request
Jan 10, 2026
…NVIDIA#2723) Signed-off-by: John St John <jstjohn@nvidia.com> Signed-off-by: John St. John <jstjohn@nvidia.com>
github-merge-queue Bot
pushed a commit
that referenced
this pull request
Jan 14, 2026
Signed-off-by: John St John <jstjohn@nvidia.com> Signed-off-by: John St. John <jstjohn@nvidia.com> Signed-off-by: Boxiang Wang <boxiangw@nvidia.com> Co-authored-by: John St John <jstjohn@nvidia.com> Co-authored-by: Boxiang Wang <boxiangw@nvidia.com>
github-merge-queue Bot
pushed a commit
that referenced
this pull request
Jan 14, 2026
Signed-off-by: John St John <jstjohn@nvidia.com> Signed-off-by: John St. John <jstjohn@nvidia.com> Signed-off-by: Boxiang Wang <boxiangw@nvidia.com> Co-authored-by: John St John <jstjohn@nvidia.com> Co-authored-by: Boxiang Wang <boxiangw@nvidia.com>
ko3n1g
pushed a commit
to ko3n1g/Megatron-LM
that referenced
this pull request
Jan 20, 2026
…NVIDIA#2723) Signed-off-by: John St John <jstjohn@nvidia.com> Signed-off-by: John St. John <jstjohn@nvidia.com>
maanug-nv
pushed a commit
to maanug-nv/Megatron-LM
that referenced
this pull request
Jan 20, 2026
…NVIDIA#2723) Signed-off-by: John St John <jstjohn@nvidia.com> Signed-off-by: John St. John <jstjohn@nvidia.com>
maanug-nv
pushed a commit
to maanug-nv/Megatron-LM
that referenced
this pull request
Jan 21, 2026
Signed-off-by: John St John <jstjohn@nvidia.com> Signed-off-by: John St. John <jstjohn@nvidia.com> Signed-off-by: Boxiang Wang <boxiangw@nvidia.com> Co-authored-by: John St John <jstjohn@nvidia.com> Co-authored-by: Boxiang Wang <boxiangw@nvidia.com>
maanug-nv
pushed a commit
to maanug-nv/Megatron-LM
that referenced
this pull request
Jan 21, 2026
Signed-off-by: John St John <jstjohn@nvidia.com> Signed-off-by: John St. John <jstjohn@nvidia.com> Signed-off-by: Boxiang Wang <boxiangw@nvidia.com> Co-authored-by: John St John <jstjohn@nvidia.com> Co-authored-by: Boxiang Wang <boxiangw@nvidia.com>
dimapihtar
added a commit
to dimapihtar/Megatron-LM
that referenced
this pull request
Feb 4, 2026
…e system (NVIDIA#2723)" This reverts commit 41cedd6. Signed-off-by: dimapihtar <dpihtar@gmail.com>
ko3n1g
added a commit
to ko3n1g/Megatron-LM
that referenced
this pull request
Feb 4, 2026
…e system (NVIDIA#2723)" This reverts commit 41cedd6.
6 tasks
daiyaanarfeen
pushed a commit
to daiyaanarfeen/Megatron-LM
that referenced
this pull request
Feb 23, 2026
…NVIDIA#2723) Signed-off-by: John St John <jstjohn@nvidia.com> Signed-off-by: John St. John <jstjohn@nvidia.com>
yangbofun
pushed a commit
to xlm-research/Megatron-LM
that referenced
this pull request
May 22, 2026
…NVIDIA#2723) Signed-off-by: John St John <jstjohn@nvidia.com> Signed-off-by: John St. John <jstjohn@nvidia.com>
terminator123
pushed a commit
to 021ai/Megatron-LM
that referenced
this pull request
Aug 3, 2026
…NVIDIA#2723) Signed-off-by: John St John <jstjohn@nvidia.com> Signed-off-by: John St. John <jstjohn@nvidia.com>
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.
What does this PR do ?
This PR removes the hard-coded wd_mult, and brings back the flexibility of the previous lambda API while allowing users to override a number of different optimizer or scheduler configs per layer. This ideas were discussed in the design document "Optimizer param lookup refactor idea".
Contribution process
flowchart LR A[Pre-checks] --> B[PR Tests] subgraph Code Review/Approval C1[Expert Review] --> C2[Final Review] end B --> C1 C2 --> D[Merge]Pre-checks
Core 0.8)Code review
The following process is enforced via the CODEOWNERS file for changes into
megatron/core. For changes outside ofmegatron/core, it is up to the PR author whether or not to tag the Final Reviewer team.For MRs into `main` branch
(Step 1): Add PR label
Expert Review(Step 2): Collect the expert reviewers reviews
Expert Reviewlabel when your PR is ready for review.Final Review might get declined if these requirements are not fulfilled.
(Step 3): Final Review
Final Reviewlabel(Optional Step 4): Cherry-pick into release branch
If this PR also needs to be merged into
core_r*release branches, after this PR has been merged, selectCherry-pickto open a new PR into the release branch.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.Merging your PR
Any member of core-adlr and
core-nemowill be able to merge your PR.