Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
[Onprem] Support for Different Type of GPUs + Small Bugfix #1356
[Onprem] Support for Different Type of GPUs + Small Bugfix #1356
Changes from 2 commits
75a8ec6
b9f152c
c5993c9
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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 want to add
TITAN Xp
(used in a RISE server)?Also do you think
nvidia-smi --list-gpus
is more robust for detecting #num-gpus as it's agnostic to gpu names?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.
+1, we should think about how we can do away with this list and use just
nvidia-smi
to parse the resources available. If this PR is time-sensitive, we can do it in a different PRThere 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.
We can do this in a separate Pr imo. There has to be a better way to detect GPUs, even with onprem cluster wihtout
nvidia-smi
installed ( as was this code's assumption, works on all machines with linux/unix). Very interested in discussion for this.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 it should be a safe assumption? If
nvidia-smi
is not installed, very likely Ray will also fail to schedule CUDA jobs.If we want less assumption, Ray's approach of listing
/proc/driver/nvidia/gpus
https://github.com/ray-project/ray/blob/f39d323ed5916b67042407231f5b91851e8fa0b5/python/ray/_private/resource_spec.py#L281 should be better.
It looks pretty robust (similar to
lspci
, only assume nvidia-driver is installed) and name-agnostic.This will auto cover
TITAN Xp
andTITAN V
that currently not in the list but used in RISE's and Woosuk's server? Does that make sense?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.
It seems a bit different on Windows (how Ray handles it), which is the OS used by one of my family members (along with
nvidia-smi
not being available despite being able to use the GPU). I'll look deeper into it for a future PR.