-
Notifications
You must be signed in to change notification settings - Fork 669
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
Decouple ray submitter, worker, and head resources #5933
Conversation
146c464
to
75c0ceb
Compare
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.
Thank you for this!
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #5933 +/- ##
==========================================
- Coverage 36.95% 36.95% -0.01%
==========================================
Files 1310 1310
Lines 131401 131451 +50
==========================================
+ Hits 48556 48574 +18
- Misses 78631 78656 +25
- Partials 4214 4221 +7
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
75c0ceb
to
c9fb595
Compare
9ee91c1
to
c5185dd
Compare
Signed-off-by: Jason Parraga <[email protected]>
c5185dd
to
2ab33a1
Compare
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.
Awesome. Thank you!
Tracking issue
Related to #5666
Why are the changes needed?
If you try to use the Ray plugin for GPU related workloads the submitter pod ends up consuming as many GPUs as the heads/worker nodes.
What changes were proposed in this pull request?
This pull request introduces resources fields in the worker and head node specs. It then uses the task resources for the submitter pod.
How was this patch tested?
Unit tests
Setup process
Screenshots
Check all the applicable boxes
Related PRs
flytekit PR will come
Docs link
TBA