-
Notifications
You must be signed in to change notification settings - Fork 26.3k
Reland of benchmark code #43428
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
Reland of benchmark code #43428
Conversation
💊 CI failures summary and remediationsAs of commit c234a5e (more details on the Dr. CI page):
ci.pytorch.org: 1 failedThis comment was automatically generated by Dr. CI (expand for details).Follow this link to opt-out of these comments for your Pull Requests.Please report bugs/suggestions on the GitHub issue tracker or post in the (internal) Dr. CI Users group. This comment has been revised 15 times. |
788fc3a to
d6695ea
Compare
d6695ea to
c234a5e
Compare
facebook-github-bot
left a comment
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.
@albanD has imported this pull request. If you are a Facebook employee, you can view this diff on Phabricator.
|
Consider using benchmarking utilities from torch/utils/_benchmark, they handle a lot of this for you (automatically synchronizing for cuda, assembling measurements, computing mean and var) |
|
@ngimel Ho I didn't knew these existed. I'll take a look, thanks! |
Reland of the benchmark code that broke the slow tests because the GPU were running out of memory