-
Notifications
You must be signed in to change notification settings - Fork 24.9k
Introduce a new API torch.accelerator.get_mem_info #156812
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
base: gh/guangyey/163/base
Are you sure you want to change the base?
Conversation
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/156812
Note: Links to docs will display an error until the docs builds have been completed. ❌ 2 New Failures, 3 Unrelated FailuresAs of commit ab5c4b2 with merge base 178515d ( NEW FAILURES - The following jobs have failed:
FLAKY - The following jobs failed but were likely due to flakiness present on trunk:
BROKEN TRUNK - The following job failed but were present on the merge base:👉 Rebase onto the `viable/strict` branch to avoid these failures
This comment was automatically generated by Dr. CI and updates every 15 minutes. |
Isn't this duplicated with other existing APIs? |
Unlike |
Currently, in
Changing these code with another |
@albanD Do you think if introducing this API is reasonable. |
Stack from ghstack (oldest at bottom):
Motivation
torch.cuda.mem_get_info
andtorch.xpu.mem_get_info
are widely used in other popular repos, such asThis PR introduces a unified API
torch.accelerator.get_memory_info
to cover this scenario.