Repository navigation
perf(nemotron): add Nemotron 3.5 Lightning GB300 recipes - #5693
Conversation
Signed-off-by: Malay Nagda <malayn@nvidia.com>
|
Auto-sync is disabled for draft pull requests in this repository. Workflows must be run manually. Contributors can view more details about this message here. |
Signed-off-by: Malay Nagda <malayn@nvidia.com>
|
LGTM Clean mirror of the existing GB200 Nemotron 3.5 Lightning perf recipes onto GB300, with matching unit-test coverage. Verified the four new config functions differ from their GB200 twins only in the intended env-var/topology set, and that the test registries (_GB300_RECIPES, _GB_FSDP_RECIPES, base-recipe pairs, finalize factories, and the MTP / topology / FSDP-defaults / CutDSL assertions) all reference the new functions. The dump_perf_configs.py entries also include the fsdp variant. Minor (non-blocking): in _build_nemotron_3_5_lightning_gb300_mxfp8, moe_hybridep_num_sms = 16 is redundant. The GB300 nano MXFP8 builder already sets it to 16 (unlike the GB200 nano MXFP8 builder, which sets 32, where the override is meaningful). Harmless, just a copy artifact. Suggested test cases:
|
Signed-off-by: Malay Nagda <malayn@nvidia.com>
Signed-off-by: Malay Nagda <malayn@nvidia.com>
What does this PR do?
Adds canonical Nemotron 3.5 Lightning throughput-benchmark recipes for an 8-GPU GB300 system.
megatron.bridge.perf_recipes.nemotronhand registers them in the performance-config inventory.These are benchmark recipes for upper-bound throughput measurement, not production convergence recipes.
Testing
uv run --with pre-commit --no-project pre-commit run --all-files— passed.fast-hadamard-transformbecause its isolated build environment does not declaretorch, and the existing.venvdoes not containpytestortorch.