microsoft / microsoft/nnscaler
[Roadmap] nnScaler Roadmap Q3 2025
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 136
- Forks
- 26
- PR merge metrics
- No merged PRs in 30d
Description
Large Scale MoE Support
Start from deepseek v3, SOTA open source models are all MoE models with parameter numbers ranging from 100B to 1T. We want to refine existing implementation to automatically generate high performance distributed plans for these models efficiently.
Tracer & Parser
- trace large model in less than 10 minutes
Schedule
- integrate zero-bubble schedule
- integrate dual pipeline
- implement and test computation and communication overlap
AutoDist
- support partitioning multiple dimension
- support profiling operators with communication, like ring-attention
- add interleaved pipeline parallelism to the search space
- refine partition constraint interface: add constraint by torch's full qualified name
Codegen
- reduce code generation time when scale unit is large, like 128 devices
Runtime
- improve saving checkpoint
- support parameter in bf16, but accumulated in fp32 in reducer
- support multiple parameter groups, like muon optimizer
- support dynamic sequence length and forbidden certain dims to be partitioned
- dedup checkpoints for modules not parallelized
User experience
- add examples for hooks, e.g., logging router logits in MoE
- integrate nnScaler in RL training framework, like veRL
- bump transformers version in
examplefolder
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
This is a broad Q3 roadmap spanning the tracer, parser, schedules, AutoDist, code generation, runtime, and user experience. Start by choosing one unchecked item and reviewing the corresponding nnScaler subsystem, using the DeepSeek V3 and MoE context where relevant. Done requires completing that item and validating its stated performance, compatibility, or example outcome.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, pytorch
- Domain
- compilers, distributed-systems, machine-learning
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100