Configure FSDP to keep module params #12074
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR do ?
This PR aims to fix a bug introduced in Transformer Engine 1.14 when running with FSDP.
Transformer Engine 1.14 changed its LayerNorm and RMSNorm implementation to use a prototype operation-based API (see NVIDIA/TransformerEngine#1033). This is a generic API intended for kernel fusion and its forward pass requires calling
torch.nn.Module.parameters
to interface with PyTorch's autograd infrastructure. However, the default behavior of PyTorch FSDP is to remove all module parameters and manage them viaFlatParameter
s. Since TE modules couldn't access their parameters, we got the following error:This PR changes the FSDP configuration with
use_orig_params=True
so that TE modules can still access their parameters.Collection: NLP
Changelog
Usage
Run GPT, e.g. with the config at https://github.com/NVIDIA/NeMo/blob/main/examples/nlp/language_modeling/conf/megatron_gpt_config.yaml.
Some relevant options:
model.transformer_engine=True
model.fsdp=True
,fsdp_sharding_strategy=full
GitHub Actions CI
The Jenkins CI system has been replaced by GitHub Actions self-hosted runners.
The GitHub Actions CI will run automatically when the "Run CICD" label is added to the PR.
To re-run CI remove and add the label again.
To run CI on an untrusted fork, a NeMo user with write access must first click "Approve and run".
Before your PR is "Ready for review"
Pre checks:
PR Type:
Who can review?
Anyone in the community is free to review the PR once the checks have passed.
Contributor guidelines contains specific people who can review PRs to various areas.
Additional Information
parameters
function in op backward pass TransformerEngine#1403 unsuccessfully attempted to fix this error