Conversation
meta-cla
bot
added
the
CLA Signed
d4l3k
force-pushed
the
d4l3k/ucc
branch
3 times, most recently
from
568b37c to
df691bd
Compare
d4l3k
changed the title
d4l3k
force-pushed
the
d4l3k/ucc
branch
3 times, most recently
from
3aac734 to
5813930
Compare
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This adds a UCC and MPI backends for torchcomms as a prototype. These backends were tested on single node with tcp and shm and compared against the Gloo TCP backend. This is prototyping switching off of gloo to a more widely maintained backend.
Key considerations:
See the full report at https://github.com/meta-pytorch/torchcomms/blob/d4l3k/ucc/comms/torchcomms/tests/perf/py/gloo_vs_ucc_report.md with benchmark results.