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

[Feature] Support Nvidia A100 accelerator_type #21557

Closed
2 tasks done
vicyap opened this issue Jan 12, 2022 · 0 comments · Fixed by #21558
Closed
2 tasks done

[Feature] Support Nvidia A100 accelerator_type #21557

vicyap opened this issue Jan 12, 2022 · 0 comments · Fixed by #21558
Labels
enhancement Request for new feature and/or capability triage Needs triage (eg: priority, bug/not-bug, and owning component)
Milestone

Comments

@vicyap
Copy link
Contributor

vicyap commented Jan 12, 2022

Search before asking

  • I had searched in the issues and found no similar feature requirement.

Description

I could not find Nvidia's A100 as an accelerator type in https://github.com/ray-project/ray/blob/master/python/ray/util/accelerators/accelerators.py. I'm curious if this is simply missing or if there's a reason it's not included.

Use case

AWS offers the A100 in the p4d.24xlarge instance type. We use that instance type along with p3 (Nvidia V100). I would like to add A100 so code is more uniform.

from ray.util.accelerators import NVIDIA_TESLA_A100

@ray.remote(num_gpus=1, accelerator_type=NVIDIA_TESLA_A100)
def train():
    ....

Related issues

I found #12413, but that issues is trying to make use of the A100's MIG (multi-instance gpu) feature. That feature would be cool but will take longer to merge.

Are you willing to submit a PR?

  • Yes I am willing to submit a PR!
@vicyap vicyap added the enhancement Request for new feature and/or capability label Jan 12, 2022
vicyap added a commit to vicyap/ray that referenced this issue Jan 12, 2022
@DmitriGekhtman DmitriGekhtman added the triage Needs triage (eg: priority, bug/not-bug, and owning component) label Jan 12, 2022
@DmitriGekhtman DmitriGekhtman added this to the Serverless Autoscaling milestone Jan 12, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Request for new feature and/or capability triage Needs triage (eg: priority, bug/not-bug, and owning component)
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants