-
Notifications
You must be signed in to change notification settings - Fork 976
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
Fix up state with xla + performance regression #2634
Conversation
device = "cuda" | ||
self.device = torch.device(device, self.local_process_index) | ||
if device == "xla": | ||
self.device = xm.xla_device() |
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.
We don't do this here (the else
), it happens during set_replication
later and that's not the same as setting set_device
(it spawns up the TPU DDP)
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.
That's really annoying thanks for quickly fixing this, LGTM.
The check_cuda_p2p_ib_support
should certainly be amended now. For the xla issue, I agree, let's wait for confirmation.
The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update. |
Looks to have fixed our issues here: #2629 :) Merging |
What does this PR do?
The one un-testible backend of course is the one that had issues 😓
waiting to hear back but should fix #2629, if so I'll do a patch with this PR 🤞
Fixes #2629
Fixes #2633
Before submitting
Pull Request section?
to it if that's the case.
documentation guidelines, and
here are tips on formatting docstrings.
Who can review?
Anyone in the community is free to review the PR once the tests have passed. Feel free to tag
members/contributors who may be interested in your PR.
@BenjaminBossan