
from megatron-bridge637
Guides enabling and validating MoE expert-parallel communication overlap in Megatron-Bridge to hide dispatch/combine latency and improve throughput.
This skill explains how to enable and validate Expert-Parallel (EP) overlap for Mixture-of-Experts (MoE) models in Megatron-Bridge. It describes configuration options (overlap_moe_expert_parallel_comm, delay_wgrad_compute), dispatcher choices (alltoall vs flex), minimal working configs, runtime constraints, and verification steps including unit tests and log checks. The guidance is practical: start with the alltoall dispatcher for compatibility, then move to flex (DeepEP/HybridEP) on supported GPUs for higher overlap.
Use this skill when running MoE models where dispatch/combine communication is a measurable bottleneck and you want to trade memory/time to improve throughput. It's appropriate for tuning throughput on multi-GPU nodes, diagnosing throughput regressions related to EP settings, or validating complex interactions (delayed wgrad, CUDA graphs). Avoid using it during early bring-up, or when full activation recompute is enabled.
alltoall and flex dispatchers, minimal runnable commands, verification steps, and known failure modes and fixes.This is a technical, code-focused skill useful to agents that can read code, run tests, and edit training configs (Copilot-style assistants, developer-facing agents). It assumes access to a developer environment with Python and the training repo.
NVIDIA Megatron-Bridge MoE expert-parallel overlap skill. The SKILL.md content is no longer accessible (404 on GitHub), and no scripts were bundled. Only metadata (name, description, tags) was available for review. Very niche — targets Megatron-LM MoE training performance tuning, relevant to only a small subset of ML engineers working with NVIDIA's distributed training framework.
SKILL.md body was null in DB and GitHub returns 404. Skill may be deleted from source repo. Architecture score low due to missing content and no structure to evaluate. Quality score low because there's nothing substantive to review — only a short_description and tags. Usefulness is niche (MoE overlap tuning for Megatron). No security concerns found in available metadata.