-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[FSDP][Example] Fix FSDP example for use_orig_params=False
#3298
base: main
Are you sure you want to change the base?
Conversation
Signed-off-by: SumanthRH <[email protected]>
Signed-off-by: SumanthRH <[email protected]>
Signed-off-by: SumanthRH <[email protected]>
Signed-off-by: SumanthRH <[email protected]>
Nice catch, I didn't know about that. |
The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update. |
Signed-off-by: SumanthRH <[email protected]>
This issue has been automatically marked as stale because it has not had recent activity. If you think this still needs to be addressed please comment on this thread. Please note that issues that do not follow the contributing guidelines are likely to be ignored. |
not stale |
@SumanthRH what this hints at is when we do
Would you be willing to tackle it this way instead? It's critical we maintain the |
Yes that's much better behaviour. Let me take a stab at it this week. |
What does this PR do?
Fixes the FSDP example for
use_orig_params=False
. I recently started using FSDP via Accelerate and hit some roadblocks due to rough edges in documentation and examples. Some improvements in this PR:use_orig_params=False
should be the recommended route all the time (full param/ lora), since it's typically more efficient.use_orig_params=False
requires model preparation before optimizer instantiation. This is a silent failure - I noticed that loss didn't decrease in this case. I believe it is best if.prepare
has extra validation for this and raise an Error to the user. (Might do this in a separate PR if I get time). The example prepares everything together because it assumesuse_orig_params
is True from this PR: fsdp refactoring #2177use_orig_params
. I found a note from an older version so I brought it back.SHARD_GRAD_OP
is a bit different from Zero Stage 2, this PR adds a tiny note.Fixes # (issue)
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.
cc @muellerzr