Skip to content
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

GPU Peer2Peer communication via --num_ranks_in_server argument #60

Open
siddharth9820 opened this issue Nov 19, 2020 · 1 comment
Open

Comments

@siddharth9820
Copy link

siddharth9820 commented Nov 19, 2020

I wanted to get a better understanding of the argument --num_ranks_in_servers in the image classification runtime referenced here. I had the following questions:

  1. Should it be equal to the number of GPUs per node?
  2. In the readme for runtime, I do not see any mention of this argument in the instructions to run the framework. From my understanding, assigning the correct value for this argument is important to enable Peer2Peer communication among GPUs using gloo. Otherwise, pipedream switches to a suboptimal communication routine by yanking the data off to the CPU and then sending it via gloo. Please let me know if I should be using this argument to operate the framework in it's most optimal format. If yes, I'd suggest an update of the readme file.
@siddharth9820
Copy link
Author

Wanted to follow up on this, we are using pipedream in our experiments and wanted to be sure of the optimal settings to run the framework.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant