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.

Sign up for GitHub

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

Jump to bottom

[Feature] A doc about the best practice for mapping Ray resources to K8s pod resources #2804

Open
1 of 2 tasks
kevin85421 opened this issue Jan 22, 2025 · 0 comments
Open
1 of 2 tasks

[Feature] A doc about the best practice for mapping Ray resources to K8s pod resources #2804

kevin85421 opened this issue Jan 22, 2025 · 0 comments
Labels
enhancement New feature or request triage

Comments

@kevin85421
Copy link
Member

kevin85421 commented Jan 22, 2025 •
edited
Loading

Search before asking

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

Description

It's common for users to ask about the best resource configurations for the Ray head Pod and Ray worker Pods.

Example questions:

  • How much resources are required for the head Pod?
  • Should I set resource limits?
  • If I want to deploy 4 Ray Actors, each with num_cpus=2, what is the best configuration for the Ray Pod? For example, should the resource request be 8 CPUs and the resource limit be 12 CPUs?

Use case

No response

Related issues

No response

Are you willing to submit a PR?

  • Yes I am willing to submit a PR!
@kevin85421 kevin85421 added enhancement New feature or request triage labels Jan 22, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request triage
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@kevin85421