-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
document deepspeed.initialize() #644
Conversation
We currently briefly reference this call related to MPI/AzureML environments (https://www.deepspeed.ai/getting-started/#mpi-and-azureml-compatibility) but thanks for adding it higher up since it seems others will also find this useful. |
Honestly I'd have never looked there unless I had MPI or Azure ;) Should I tweak the doc to add that it uses the NCCL backend? |
Haha totally understandable, it was kind of hidden away it seems :) It also needs to be added to our RTD documentation as well. I'll do that right now actually. You can choose the backend as a parameter, but it does default to NCCL and that's primarily what we've tested everything with across the project. Feel free to add some text about NCCL though. |
Thank you, @jeffra I added the note about the default, but I couldn't find |
Just added it to RTD docs with this PR #645 |
If you want to add a link to it, it's live now: https://deepspeed.readthedocs.io/en/latest/initialize.html#distributed-initialization |
That's excellent. Added the link. |
As a follow up to the very helpful suggestion I received at #633 I propose this doc update.
Thank you!
Fixes: #633
@jeffra