-
Notifications
You must be signed in to change notification settings - Fork 88
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
18. Investigating approaches for nondeterministic jobs such as ML training #26
Comments
3 tasks
Do you have a strong preference between CPU centric model training (e.g. Spark, NumPy) vs GPU centric model training (Tensorflow, Keras, PyTorch)? Curious b/c of how it would impact hardware assumptions for the firecracker host. |
I'm assuming we'll get CPU working well first
…On Mon, 21 Feb 2022, 15:11 Wes Foyd, ***@***.***> wrote:
Do you have a strong preference between CPU centric model training (e.g.
Spark, NumPy) vs GPU centric model training (Tensorflow, Keras, PyTorch)?
Curious b/c of how it would impact hardware assumptions for the firecracker
host.
—
Reply to this email directly, view it on GitHub
<#26 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AACATUTSRPWIBRDEYEPNCALU4JI2HANCNFSM5NGJQXRQ>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The text was updated successfully, but these errors were encountered: