Skip to content

[ROADMAP][2026 Q3] Megatron Core Roadmap #5676

Open

Description

@sbhavani

This roadmap tracks the key Megatron Core features, enhancements, and improvements originally planned for Q3 2026, including their carry-over status as of October 15, 2026. The 26.08 release has been delivered; remaining items continue beyond Q3 without a new delivery commitment. This is a tentative roadmap and subject to change.

Last updated: October 15, 2026.

Status convention: “delivered on main” or “delivered on dev” means the linked implementation has merged into that branch; it does not imply inclusion in 26.08 or complete end-to-end qualification. Items marked “in progress” may have merged foundations with integration or validation still outstanding.

For detailed information on past releases, see the Megatron Core release notes. For the previous quarterly roadmap, see Q2 2026 Roadmap #4997. For component-specific plans and status, see the Q3 MoE Roadmap #6757 and Q3 Megatron FSDP v2 Roadmap #6812.


Q3 Roadmap (26.08 shipped)

MoE

Model Architecture and Support

Parallelism

Performance and Memory

Precision and Optimizers

Inference

Reinforcement Learning

Multimodal

* : Feature was developed on the dev branch first. Branch availability is stated above; check release notes for inclusion in a packaged release.


How to Provide Feedback

We welcome community input on prioritization. Please:

  1. React to items you would like prioritized.
  2. Comment on this issue with use cases, constraints, and hardware / model configurations.
  3. Open focused feature requests with the enhancement label.
  4. Contribute pull requests for roadmap items where possible.

Credits

This roadmap reflects the collective efforts of NVIDIA, external contributors, and the Megatron Core community.

Activity

  1. pinned this issue on Jul 6, 2026
  2. satwiksps commented on Jul 7, 2026

    @satwiksps

    Hello @sbhavani
    I would like to work on moving quantize.py to the root folder.

  3. sbhavani commented on Jul 7, 2026

    @sbhavani
    ContributorAuthor

    @satwiksps thanks for volunteering! that's not the best first issue. I'll take a look through our roadmap/issues and try to label some good first issues this week for you to take on.

  4. wujingyue commented on Jul 7, 2026

    @wujingyue
    Contributor

    @sbhavani FYI, I made a project tracker for MFSDP: https://github.com/orgs/NVIDIA/projects/276. Feel free to add a link into the roadmap.

  5. z1ying commented on Jul 8, 2026

    @z1ying

    thanks for volunteering! that's not the best first issue. I'll take a look through our roadmap/issues and try to label some good first issues this week for you to take on.

    Hi @sbhavani, I‘d also love to contribute. Looking forward to the good first issues!

  6. lk137095576 commented on Jul 30, 2026

    @lk137095576

    @sbhavani Are we still doing Echo? #2368 .
    I see it's gone from the Q3 2026 roadmap. Moonep might be a better option?

  7. sbhavani commented on Aug 5, 2026

    @sbhavani
    ContributorAuthor

    @lk137095576 please see #6134 for initial MoonEP support

  8. adityaghai07 commented on Sep 12, 2026

    @adityaghai07
    Contributor

    @sbhavani — I've opened #7274 (draft) for the "PTQ and QAD documentation" item. Happy to close it if this is already owned internally.

    Two gaps it addresses:

    • PTQ material exists under examples/post_training/modelopt/ but isn't surfaced in the docs site. ModelOpt is only referenced in get-started/overview.md and get-started/install.md, with no page in the Advanced Features toctree.
    • QAD has no user-facing documentation. --qad-train-target {base,mtp,both} and _freeze_for_qad are implemented, but QAD only appears in source comments. This includes the detail that freezing one side of an MTP model also freezes that side's router bias terms, which are updated from token counts rather than gradients.

    The new page covers quantize → evaluate → distil → export, plus multi-node Slurm, using nvidia/NVIDIA-Nemotron-3-Nano-30B-A3B-BF16 as the worked example. Flags and defaults are taken from the source rather than the existing prose.

    One question I've flagged on the PR: the _freeze_for_qad docstring calls the MTP target the "production two-phase recipe" but doesn't specify the ordering. Confirmation that distil base → train heads is correct would be helpful.

  9. 0z5a commented on Sep 18, 2026

    @0z5a

    Hi @sbhavani , I’d like to investigate temporary-buffer and pad/compact overhead in NCCLAllGatherDispatcher’s ragged prefill path, keeping the existing collective protocol unchanged. I’d validate correctness, peak memory, and end-to-end prefill latency on multi-GPU L20.

  10. VikingDeng commented on Oct 23, 2026

    @VikingDeng

    Hi @sbhavani and @asolergi-nv, I read the SFTDataset note in this roadmap, the closed #5017, and the current sft_dataset.py, varlen_dataset.py, data_schedule.py and sft_tokenizer.py. I'd like to take this one. My first PR would add a pre-tokenized .bin/.idx reader with an assistant-only loss-mask sidecar to the existing VarlenDataset and DP-balanced scheduler path, tested on CPU with synthetic data and then a short 1B run on one GPU. One scope question: is that enough for a first PR, or do you want the full #5017-style core SFTDataset with MFFD packing and thinking/tool masks?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions