Skip to content
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

[Runpod] Use consistent naming for A100s #64

Open
romilbhardwaj opened this issue Mar 13, 2024 · 2 comments
Open

[Runpod] Use consistent naming for A100s #64

romilbhardwaj opened this issue Mar 13, 2024 · 2 comments

Comments

@romilbhardwaj
Copy link
Contributor

On runpod, A100-80GB is listed separately asA100-80GB-SXM. Since SkyPilot doesn't currently distinguish between PCIE and SXM4 variants, we should probably change A100-80GB-SXM to A100-80GB in our catalog.

image image
@Michaelvll
Copy link
Collaborator

On runpod, A100-80GB is listed separately asA100-80GB-SXM. Since SkyPilot doesn't currently distinguish between PCIE and SXM4 variants, we should probably change A100-80GB-SXM to A100-80GB in our catalog.

image image

On RunPod, there are both PCIE and SXM version on the same region. Changing to A100-80GB will make it fail to choose those SXM instance types unless a user specify the instance type directly. Does that sound good to you?

@romilbhardwaj
Copy link
Contributor Author

I see... I was confused because A100-80GB is SXM4 on gcp, but looks like on runpod we will provision PCIE unless user explicitly asks for A100-80GB-SXM.

For consistency, should we make A100-80GB on runpod correspond to the SXM4 instance, and list A100-80GB-PCIE separately?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants