-
Notifications
You must be signed in to change notification settings - Fork 304
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
[REVIEW]Multi-trainers cugraph-DGL examples #3212
[REVIEW]Multi-trainers cugraph-DGL examples #3212
Conversation
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## branch-23.04 #3212 +/- ##
===============================================
Coverage ? 56.27%
===============================================
Files ? 153
Lines ? 9662
Branches ? 0
===============================================
Hits ? 5437
Misses ? 4225
Partials ? 0 Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
@VibhuJawa is this is still WIP? I thought you said this was ready for review. |
Sorry for the confusion. This is still WIP. Will let you know when it is ready for review |
Please note that this example is failing because of a bug that i am trying to triage. That said, the bug is independent of the PR so we can probably review it. |
…exbarghi-nv/cugraph into cugraph-gnn-fix-sample-index
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.
Looks ok, just had a couple comments that don't need to hold up merging this PR.
/merge |
This PR adds a working Multi-GPU Graph (on 2 dask workers) being trained/loaded on multiple pytorch trainers. (3)
Todo:
At 1 second we become bottlenecked by sampling dask cluster, but we see perf improvement by going from
1 GPU
->2GPU
.On OBGN-Products
This PR depends upon: #3393
CC: @rlratzel , @alexbarghi-nv , @BradReesWork