Back to Skills

nemo-mbridge-perf-moe-dispatcher-selection

Choose the right MoE token dispatcher (`alltoall`, DeepEP, or HybridEP) for the hardware, EP degree, and optimization stage. Summarizes patterns from DSV3, Qwen3, Qwen3-Next, and VLM bring-up work.

2,773stars323forksUpdated 8/3/2026

Security Assessment

Safe(95/100)
Security Score95/100

About nemo-mbridge-perf-moe-dispatcher-selection

nemo-mbridge-perf-moe-dispatcher-selection is an NVIDIA decision-support skill that helps engineers choose the right Mixture-of-Experts (MoE) token dispatcher — alltoall, DeepEP, or HybridEP — in Megatron-Bridge based on hardware, expert-parallelism (EP) degree, and optimization stage. It solves the problem of picking a dispatcher without expensive trial-and-error by distilling patterns observed across DSV3, Qwen3, Qwen3-Next, and MoE VLM bring-up work into quick decision tables (by hardware and by EP size) and model-family guidance.

The skill's main value is its rounded evidence summary. It stresses a backend availability gate: a dispatcher timing is meaningless until the container proves the selected backend package (DeepEP or HybridEP) is actually importable, and alltoall is the correctness fallback when they are missing. It records concrete smoke-run observations (for example a Qwen3 30B A3B run on H100 with EP=16 where DeepEP and HybridEP selected the flex backend but failed before the first iteration because the packages were not installed) and broad MFU trends on GB200/GB300 NVL72 systems, while repeatedly cautioning that dispatcher wins are workload-dependent and should be tested rather than assumed.

It targets performance and infrastructure engineers training large MoE models, or those tracing an MoE regression or crash to a dispatcher config change. The output is configuration guidance and analysis in Markdown with inline bash — no code execution, credentials, or destructive actions. NVSkills-Eval reported a 100% Security score.

FAQ

Which dispatcher should I start with?

For unknown hardware or first bring-up, start with alltoall for correctness and debugging. On H100/B200 prefer DeepEP if its runtime package is installed; on GB200/GB300 NVL72 prefer HybridEP.

Why does it insist on an availability gate?

DeepEP and HybridEP select the flex dispatcher but require their runtime packages at model construction time. If a package is missing the run fails before the first iteration, so a timing cannot be trusted until availability is proven.

Does dispatcher choice always matter?

No. At small EP the choice is usually second-order, and wins are workload- and precision-dependent (for example Qwen3-Next can be close in BF16 but favor HybridEP in FP8), so the skill advises testing rather than assuming.

What models are the patterns drawn from?

DSV3 at large scale, Qwen3 235B and 30B, Qwen3-Next, and MoE VLM bring-up work.

Does it execute anything?

No. It provides decision tables and evidence-based analysis; you apply the resulting configuration yourself.

All Files

6 files
card.yaml3.9 KB
View
skill-card.md3.9 KB
View
BENCHMARK.md4.3 KB
View
evals/evals.json1.5 KB
View
SKILL.md7.8 KB
View
skill.oms.sig4.7 KB
View

Install nemo-mbridge-perf-moe-dispatcher-selection

Download and extract the skill files to your .claude/skills/ directory.

Quick Setup:

  1. Copy the skill folder to .claude/skills/
  2. Claude will automatically detect and use the skill

Repository

nvidia/skills