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

object_detector default handler does not seem to be using multiple GPUs #201

Closed
fbbradheintz opened this issue Apr 14, 2020 · 7 comments · Fixed by #265
Closed

object_detector default handler does not seem to be using multiple GPUs #201

fbbradheintz opened this issue Apr 14, 2020 · 7 comments · Fixed by #265
Assignees
Labels
bug Something isn't working duplicate This issue or pull request already exists
Milestone

Comments

@fbbradheintz
Copy link
Contributor

The other default handlers seem to work on many GPUs without difficulty, but CloudWatch is telling me that only GPU 0 is being used by object_detector.

@fbbradheintz fbbradheintz added bug Something isn't working launch blocker labels Apr 14, 2020
@fbbradheintz fbbradheintz self-assigned this Apr 14, 2020
@harshbafna
Copy link
Contributor

@fbbradheintz : This is a issue with the current stable release of torchvision and we already have #104 open for tracking this.

To keep the default handler working, we have deliberately kept the GPU device to cuda:0.

@harshbafna harshbafna added the duplicate This issue or pull request already exists label Apr 17, 2020
@mycpuorg
Copy link
Collaborator

@harshbafna thanks for confirming.

@fbbradheintz I'm removing the launch blocker tag.

@lokeshgupta1975
Copy link
Collaborator

@mycpuorg You mentioned in your previous comment that you will remove the launch_blocker tag, but you did not. Should we?

@fbbradheintz
Copy link
Contributor Author

This is not, in fact, a problem with TorchVision, but a bug in object_detector.py. Putting up a fix shortly.

@fbbradheintz fbbradheintz removed their assignment Apr 24, 2020
@fbbradheintz
Copy link
Contributor Author

Covered by @harshbafna in #265, requested changes pending.

@harshbafna harshbafna self-assigned this Apr 27, 2020
@maaquib maaquib added this to the v0.1.1 milestone May 22, 2020
@maaquib maaquib moved this from In progress to In Testing in TorchServe v0.1.1 Issues Lifecycle May 22, 2020
TorchServe v0.1.1 Issues Lifecycle automation moved this from In Testing to Done May 26, 2020
@mycpuorg
Copy link
Collaborator

Closing this because #265

@mycpuorg
Copy link
Collaborator

Reopening because the changes have not made it to master yet

@mycpuorg mycpuorg reopened this May 26, 2020
TorchServe v0.1.1 Issues Lifecycle automation moved this from Done to In progress May 26, 2020
@maaquib maaquib closed this as completed Jun 10, 2020
TorchServe v0.1.1 Issues Lifecycle automation moved this from In progress to Done Jun 10, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working duplicate This issue or pull request already exists
Projects
No open projects
5 participants