Allow FSDP to use with torch.autocast
for bfloat16 mixed precision
#2033
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?
FSDP supports mixed precision using MixedPrecision class, it does not need to wrap forward function with
torch.autocast
.The code statement of ignoring this wrapping was added at accelerate v0.22.0, but now removed at v0.23.0
Related PRs are:
I can't find any information about why it is added or removed.
In fact, mixed precision works well even without
torch.autocast
, and even if it is needed, it does not work properly in the current version.So, I think it need to apply one of the following two options:
self.distributed_type != DistributedType.FSDP
in condition not to usetorch.autocast
DistributedType.FSDP
in this fileThe reason for 2 is that when FSDP is used, the
distributed_type
field is replaced withDistribytedType.FSDP
in this line, so I think it needs to be added to support FSDP as well.As a related issue, the MPT posted on Huggingface Hub uses the LPNorm class, but when learning with FSDP + bfloat16, the dtype changes before and after norm. It is occurred in version v0.23.0.
Before submitting
Pull Request section?
to it if that's the case.
documentation guidelines, and
here are tips on formatting docstrings.
Who can review?
Anyone in the community is free to review the PR once the tests have passed. Feel free to tag
members/contributors who may be interested in your PR.