Deprecate deepspeed #3512
Merged
Deprecate deepspeed #3512
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
mvpatel2000
reviewed
Aug 1, 2024
bandish-shah
approved these changes
Aug 2, 2024
jbloxham
approved these changes
Aug 2, 2024
snarayan21
reviewed
Aug 2, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 deprecates the usage of DeepSpeed in Composer. We have not updated DeepSpeed in a long time and do not actively maintain the integration. Composer is tightly coupled to PyTorch FSDP which provides similar functionality, and we are developing all new functionality on top of FSDP and PyTorch native, not DeepSpeed, for parallelism. Before removal we will provide a migration guide for anyone still using DeepSpeed. In the meantime, users are welcome to open a GitHub issue if they have any trouble.