-
Notifications
You must be signed in to change notification settings - Fork 6k
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
[ActorGroup] Add ActorGroup
#18960
[ActorGroup] Add ActorGroup
#18960
Conversation
One thing that stands out to me here is that GPU handling seems to be pretty specific to SGD. Any thoughts on whether some abstraction is needed? |
@richardliaw we could make this into a general |
WorkerGroup
to ray.util
WorkerGroup
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.
Thanks @amogkam, see comments below about making this slightly more generic. Let's not let "perfect" get in the way of "good" for now though.
One thing that would be extremely useful and I would ask for you to do in the next follow-up is to make this completely unit testable by abstracting out the Ray API calls. This is something I did awhile back in Serve and it has been invaluable for developer productivity & stability. If you want some advice / help on this, I'm happy to help brainstorm.
@amogkam decisions/changes in the comments SGTM, re-request once they're made? |
…er-group-experimental
…er-group-experimental
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.
Looks like a good start :)
Failing test is unrelated, going to merge |
This reverts commit 4f05bac.
Why are these changes needed?
Related issue number
Checks
scripts/format.sh
to lint the changes in this PR.