-
Notifications
You must be signed in to change notification settings - Fork 490
Upgrade PyTorch version to v2.2.1 #2279
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
Upgrade PyTorch version to v2.2.1 #2279
Conversation
|
We need to restart the Anyway, this PR is ready for the review. PTAL /assign @andreyvelich @johnugeorge |
| torch==1.13.1 | ||
| torchvision==0.14.1 | ||
| torch==2.2.1 | ||
| torchvision==0.17.1 |
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.
Should we also update the PyTorch base image in our SDK: https://github.com/kubeflow/katib/blob/master/sdk/python/v1beta1/kubeflow/katib/constants/constants.py#L55 ?
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.
Sure.
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.
Done.
| cloudml-hypertune==0.1.0.dev6 | ||
| torch==1.13.1 | ||
| torchvision==0.14.1 | ||
| torch==2.2.1 |
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.
Do we need to install torch version in requirements if we already using nvcr.io/nvidia/pytorch:24.01-py3 image ?
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.
I guess that it is no need, but I'm not sure that having separate requirements.txt would be worth it. @andreyvelich WDYT?
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.
@tenzen-y We are still installing cloudml-hypertune and Pillow in the requirements file, so I think we can keep it.
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.
Ah, I see. You meant that we should install torch and torch vision via Dockerfile, instead of requirements.txt, right?
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.
I thought torch package is already installed as part of this image nvcr.io/nvidia/pytorch:24.01-py3, isn't ?
I am not sure about torchvision tho
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.
Yes, both torch and torchvisoin are packaged in NVIDIA image.
Let me create a separate requirements.txt.
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.
Done.
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.
I think you misunderstood me.
Since torch and torchvision is installed in those image we can remove them from requirements.txt and install only cloudml-hypertune and Pillow. We don't need to separate requirements for CPU and GPU images.
Also, we can remove torch installation from examples/v1beta1/trial-images/darts-cnn-cifar10/requirements.txt
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.
Ah, I see. Thanks.
054c7a8 to
de4ef3f
Compare
| RUN pip install --prefer-binary --no-cache-dir torch==2.2.1 torchvision==0.17.1 | ||
| RUN pip install --prefer-binary --no-cache-dir -r requirements.txt |
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.
@andreyvelich Does this meet your intention?
Signed-off-by: Yuki Iwai <[email protected]>
de4ef3f to
e5c0e4b
Compare
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.
Thank you for this update @tenzen-y!
/lgtm
/approve
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: andreyvelich, tenzen-y The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Thank you for the helping! |
|
@andreyvelich Could you restart the "Go Test / Unit Test (1.26.1) (pull_request) "? |
What this PR does / why we need it:
I upgraded PyTorch version to v2.2.1.
This is a blocker of #2278
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)format, will close the issue(s) when PR gets merged):Fixes #
Checklist: