Skip to content

Epic: GPU Support on SaaS #10650

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

Open
4 of 5 tasks
atduarte opened this issue Jun 14, 2022 · 6 comments
Open
4 of 5 tasks

Epic: GPU Support on SaaS #10650

atduarte opened this issue Jun 14, 2022 · 6 comments
Labels
meta: never-stale This issue can never become stale segment: data-science Used to track issues related to data-science use cases size/M team: workspace Issue belongs to the Workspace team type: epic user-interview (discovery) Issues with direct links for interviewing users or customers

Comments

@atduarte
Copy link
Contributor

atduarte commented Jun 14, 2022

Callout: Hey 👋 Are you interested in this feature? I would be interested in talking to you: https://calendly.com/andre-gitpod/15-minute-product-feedback


We want to fully support GPUs to enable different workloads, such as data science, particularly on self-hosted installations.

Open questions:

  • Would we be able to dynamically assign GPUs to workspaces? Not right now
  • Would we be able to share one GPU between multiple workspaces? Preferably not right away, given performance and security concerns [video]
  • Would we be able to support all types of GPUs or would need to select a subset? What subset? Given the focus on SaaS, we will just pick one and go with that.
  • Are we able to confidently release GPU support for self-hosted without launching it also on SaaS? No
  • Is there a limitation on what and how many GPUs you can attach to a given instance type? We will need to research, maybe there are. Depending on that we might want one workspace per node, or multiple workspaces per node with multiple GPUs.

Options:

  • Just another class — We don't share GPUs across workspaces. We have a separate node pool / workspace class that has a defined workspace density, which equals the number of GPUs. We would launch on SaaS first, as we need to

Concerns:

  • Workspace classes are hard-coded in server. Probably resolved in Epic: Two Workspace Classes on SaaS #8261.
  • The user will have to keep on changing their user settings to use GPUs or not. We should have workspace class project setting. And in the future, it might make sense to allow Data Scientist to select whenever they open the workspace or inside the workspace.

Dependencies:

  • (for self-hosted) Self-hosted will need to be able to configure multiple workspace classes.
  • (Preferably) Per project workspace class setting.
  • (Must) Possibility of scaling a node pool to zero.

Things we know we will have to do:

Related request: https://github.com/gitpod-io/customers/issues/24

@atduarte atduarte moved this to In Discovery in 🌌 Workspace Team Jun 14, 2022
@atduarte atduarte changed the title Epic: GPU Support - GA Epic: GPU Support on SaaS Jun 17, 2022
@atduarte atduarte added size/M team: workspace Issue belongs to the Workspace team labels Jun 20, 2022
@sheffier
Copy link

Really expecting to try GPU support! please ping me as soon as it can be tested

@singhsidhukuldeep
Copy link

singhsidhukuldeep commented Jul 24, 2022

Can't wait to try GPUs. Please update as soon as we can try 😃

Also as a small request can we have CUDA enabled GPUs with CUDA already working out of the box?

@KangOxford
Copy link

Please ADD GPU support!!! I will pay the bill.

@knshkp
Copy link

knshkp commented Sep 19, 2022

Please ADD GPU support

@loujaybee loujaybee added the user-interview (discovery) Issues with direct links for interviewing users or customers label Oct 11, 2022
@stale
Copy link

stale bot commented Jan 10, 2023

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the meta: stale This issue/PR is stale and will be closed soon label Jan 10, 2023
@gtsiolis gtsiolis added meta: never-stale This issue can never become stale and removed meta: stale This issue/PR is stale and will be closed soon labels Jan 10, 2023
@loujaybee loujaybee added the segment: data-science Used to track issues related to data-science use cases label Mar 1, 2023
@julien-blanchon
Copy link

Any news on this ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
meta: never-stale This issue can never become stale segment: data-science Used to track issues related to data-science use cases size/M team: workspace Issue belongs to the Workspace team type: epic user-interview (discovery) Issues with direct links for interviewing users or customers
Projects
No open projects
Status: No status
Development

No branches or pull requests

8 participants