-
Notifications
You must be signed in to change notification settings - Fork 402
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
[Perf] Add a CPU-based training workload #2116
Conversation
cc @andrewsykim |
|
||
|
||
if __name__ == "__main__": | ||
train_fashion_mnist(num_workers=4) |
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.
Thoughts on making num_workers configurable with an environment variable? That would it make it easier to tweak in the perf tests
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.
Same with CPUs for resources_per_worker
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.
Good idea
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.
I will ask others to work on it.
LGTM! Tested this locally and confirmed it works. Thanks @kevin85421! |
Why are these changes needed?
Our scalability test requires some CPU-based workloads. This PR uses CPU to train a MNIST model. I also can run the RayJob successfully on my devbox.
Related issue number
Checks