-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
DeepSpeed Comm. Backend v1 #1985
Conversation
Co-authored-by: Quentin Anthony <qganthony@yahoo.com> Co-authored-by: Ammar Ahmad Awan <ammar.awan@microsoft.com> Co-authored-by: Jeff Rasley <jerasley@microsoft.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I reviewed this PR with Quentin. He will take care of minor comments. @jeffra, please review this one.
…pSpeed into staging-comms-next
@SeanNaren can you take a look at the lightning test failure? We're seeing this on other PRs and in |
This reverts commit 9976681.
This PR introduces the DeepSpeed Comm. Backend (v1).
Current advanced communication schemes rely on mixing python-level communication packages (e.g. torch.distributed, mpi4py for 1-bit Adam). In order to simplify comms prototypes, we're looking to add support for custom communication backends within DeepSpeed built directly on top of their respective libraries (e.g. NCCL, MPI, etc).
This PR completes the first phase towards this goal by introducing:
deepspeed.comms
torch.distributed
calledTorchBackend
for backwards-compatibilityCo-authored-by: Quentin Anthony qganthony@yahoo.com
Co-authored-by: Ammar Ahmad Awan ammar.awan@microsoft.com
Co-authored-by: Jeff Rasley jerasley@microsoft.com