You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I had searched in the issues and found no similar feature requirement.
Description
For Ray pods configured to use GPU using one of the standard device drivers, read the number of GPUs from resource limits and automatically add that number to the --num-gpus argument of ray start, when num-gpus is not already specified.
The implementation should be straightforward and similar to existing CPU detection logic.
See the discussion in ray-project/ray#20265
Use case
This will simplify configuration for GPU workloads.
Are you willing to submit a PR?
Yes I am willing to submit a PR!
The text was updated successfully, but these errors were encountered:
We have seen cases where the users trick Ray into thinking there are more CPU --num-cpus than the actual cores allocated to the pod/container.
We also already have the raystartparams section where the users can set the num of cpus and gpus and those values will be translated into start --flags
I am fine with auto-detecting the CPU and GPU from the resource limits. One option is to add an auto-detect field that defaults to true to give the users the flexibility of not using auto-detect.
Search before asking
Description
For Ray pods configured to use GPU using one of the standard device drivers, read the number of GPUs from resource limits and automatically add that number to the
--num-gpus
argument ofray start
, when num-gpus is not already specified.The implementation should be straightforward and similar to existing CPU detection logic.
See the discussion in ray-project/ray#20265
Use case
This will simplify configuration for GPU workloads.
Are you willing to submit a PR?
The text was updated successfully, but these errors were encountered: