-
Notifications
You must be signed in to change notification settings - Fork 24.7k
Setup TorchBench in Docker #158613
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: main
Are you sure you want to change the base?
Setup TorchBench in Docker #158613
Conversation
Stack from ghstack (oldest at bottom): |
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.
This only affects the docker images used in inductor benchmarks right? Or will this make pulling docker images across all of CI slightly slower?
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.
Approving cuz this seems ok, my only question is that it does not affect anything else negatively
Yup, the size of that benchmark image increases, but it's cached on the runner. I'm trying to confirm at the moment that the cache works correctly by re-running the benchmark to warm it up. Let me confirm that before landing this change. |
Confirmed:
|
@pytorchbot merge |
This PR has pending changes requested. Please address the comments and update the PR before merging. |
@pytorchbot merge |
Merge startedYour change will be merged once all checks pass (ETA 0-4 Hours). Learn more about merging in the wiki. Questions? Feedback? Please reach out to the PyTorch DevX Team |
@pytorchbot revert -c nosignal -m "Seems to have broken trunk. See GH job link HUD commit link" |
@pytorchbot successfully started a revert job. Check the current status here. |
@huydhn your PR has been successfully reverted. |
This reverts commit cab2833. Reverted #158613 on behalf of https://github.com/ZainRizvi due to Seems to have broken trunk. See [GH job link](https://github.com/pytorch/pytorch/actions/runs/16429779764/job/46430634676) [HUD commit link](https://hud.pytorch.org/pytorch/pytorch/commit/b3c868d603e8f7b6661c93cd3d50c9a7b213ad6c) ([comment](#158613 (comment)))
This reduces the time spending to setup TorchBench in A100/H100 by another half an hour
Testing
Signed-off-by: Huy Do huydhn@gmail.com
cc @H-Huang @awgu @wanchaol @fegin @fduwjj @wz337 @wconstab @d4l3k @pragupta @voznesenskym @penguinwu @EikanWang @jgong5 @Guobing-Chen @XiaobingSuper @zhuhaozhe @blzheng @wenzhe-nrv @jiayisunx @ipiszy @chenyang78 @kadeng @muchulee8 @amjames @chauhang @aakhundov @coconutruben @Lucaskabela