[Feature] Generate rayStartParam resource flag from container resource(e.g. cpu,memory)

[chenk008]

Search before asking

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

Description

Using container.resource.cpu.limit as num-cpus default value in rayStartParams, it will help to reduce configuration redundancy. When we want to change the container resource config, we don't need to update rayStartParams.

It's the same with memory,gpu.

Use case

No response

Related issues

No response

Are you willing to submit a PR?

• Yes I am willing to submit a PR!

[Jeffwan]

Agree. container.resource.cpu.limit should be the source the truth. Let's do this

[ebr]

Perhaps this should be set from requests instead of limits? It's sometimes beneficial to not set the CPU limit, as it can introduce unwanted throttling.

[Jeffwan]

I think ray is not aware of the (limit-request) resources which leads wasting? @chenk008 do you know exact behavior on ray side?

[Jeffwan]

It has been addressed in issue #170 and we can close the issue