nemo-mbridge-recipe-recommender

Index and recommend Megatron Bridge recipes by model, GPU count, and training goal.

Updated Apr 16, 2026
One-click install
npx skills add https://github.com/sayalinvidia/sayali-skills-test --skill nemo-mbridge-recipe-recommender
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: nemo-mbridge-recipe-recommender
Source: https://github.com/sayalinvidia/sayali-skills-test/tree/main/skills/nemo-mbridge-recipe-recommender
Command: npx skills add https://github.com/sayalinvidia/sayali-skills-test --skill nemo-mbridge-recipe-recommender

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Index and recommend Megatron Bridge recipes based on a user's model, GPU count, and training goal.

Core Features & Use Cases

  • Indexes every shipped library recipe under src/megatron/bridge/recipes/ and performance recipes under scripts/performance/, enabling quick discovery and side-by-side comparison.
  • Distinguishes library vs performance recipes, provides clear entry points (run_recipe.py for training; perf scripts for throughput), and supplies dataset guidance and recommended defaults.
  • Advises on parallelism and configuration adjustments (TP/PP/CP/DP, micro-batch sizing) to fit user hardware, model size, and task requirements.

Quick Start

Ask the user for model name/size, GPU count, and training goal, then return the best-matching recipe and its entry-point commands.

Frequently Asked Questions about nemo-mbridge-recipe-recommender

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find the right Megatron Bridge recipe for my model and GPU count?

Megatron Bridge recipes are indexed based on your model name, GPU count, and training goal. The recommender matches your specifications to library and performance recipes, returning the best entry-point commands and dataset guidance.

What is the difference between library and performance recipes in Megatron Bridge?

Library recipes under src/megatron/bridge/recipes handle training via run_recipe.py, while performance recipes under scripts/performance measure throughput using dedicated perf scripts. The recommender distinguishes them to guide your entry points and defaults.

How do I configure parallelism and micro-batch sizing to avoid OOM in Megatron Bridge?

To avoid OOM, configure parallelism by ensuring TP divisibility of num_key_value_heads, staying within a node unless using interconnect, enabling SP when TP > 1, and adjusting micro-batch sizing based on DP implications.

Does Megatron Bridge support PEFT and SFT training goals?

Megatron Bridge supports PEFT and SFT training goals. The recommender indexes recipes based on your specified training objective, matching your model and hardware to appropriate library recipes for these tasks.

When do I need to enable sequence parallelism (SP) in Megatron Bridge?

You need to enable sequence parallelism (SP) when tensor parallelism (TP) is greater than 1. The recommender enforces this critical configuration rule alongside TP divisibility of num_key_value_heads to ensure valid parallelism settings.

Can I use Megatron Bridge recipes for GPU pretraining?

Yes, you can use Megatron Bridge recipes for GPU pretraining. The recommender indexes library recipes and advises on parallelism configurations like TP, PP, CP, and DP to fit your hardware, model size, and pretraining requirements.