Repository navigation
perf(llama): auto-disable PCT binding on B300 for llama pretrain - #4081
Conversation
Signed-off-by: Rahul Salagame <rsalagame@nvidia.com>
|
LGTM — the change is a clean, minimal addition to the existing PCT auto-disable guard. One observation: Intentionally broad scope: The new branch matches model_family_name llama + task pretrain + gpu b300 without filtering on model_recipe_name or compute_dtype, unlike the nemotronh branch (which gates on compute_dtype bf16) and the deepseek branch (which gates on config_variant != large_scale). This is presumably intentional (all llama pretrain on B300 needs PCT disabled), but worth confirming since future llama recipes added to the family would silently inherit this behavior. No bugs, typos, or missing docs found. Suggested test cases — The change affects setup_experiment.py PCT binding logic. It impacts all llama x pretrain x b300 combinations at experiment setup time:
|
|
/ok to test 2586005 |
|
/ok to test 56f668f |
Signed-off-by: Rahul Salagame <rsalagame@nvidia.com>
33965b9
|
/ok to test 33965b9 |
…DIA-NeMo#4081) Signed-off-by: Rahul Salagame <rsalagame@nvidia.com> Signed-off-by: Vasudevan Rengasamy <vrengasamy@nvidia.com>
adds llama × pretrain × b300 to the existing PCT auto-disable list in setup_experiment.py, alongside existing nemotronh and deepseek.