Skip to content

Epic: Create an X-Large (16 cores, 32GB) workspace class #13950

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

Closed
atduarte opened this issue Oct 18, 2022 · 5 comments
Closed

Epic: Create an X-Large (16 cores, 32GB) workspace class #13950

atduarte opened this issue Oct 18, 2022 · 5 comments
Labels
feature: workspace classes meta: stale This issue/PR is stale and will be closed soon needs visual design team: workspace Issue belongs to the Workspace team type: epic

Comments

@atduarte
Copy link
Contributor

atduarte commented Oct 18, 2022

Is your feature request related to a problem? Please describe

Users using monorepos or other big projects experience friction in using Gitpod. They either experience poor performance or limit themselves to run less tools and services at a time reducing productivity.

Describe the behaviour you'd like

Have an option to use a 16 cores, 32GB RAM, 100GB of /workspace disk on gitpod.io

ID: g1-xlarge
Name: X-Large
Description: Up to 16 vCPU, 32GB memory, 70GB disk

Additional context

Internal feedback 1, 2, ...

Front logo Front conversations

@atduarte atduarte added team: workspace Issue belongs to the Workspace team feature: workspace classes labels Oct 18, 2022
@atduarte atduarte changed the title Create an Extra Large (16 cores, 32GB) workspace class Create an XLarge (16 cores, 32GB) workspace class Oct 18, 2022
@atduarte atduarte changed the title Create an XLarge (16 cores, 32GB) workspace class Create an X-Large (16 cores, 32GB) workspace class Oct 18, 2022
@gtsiolis
Copy link
Contributor

gtsiolis commented Nov 30, 2022

Re-posting from a relevant discussion (internal):

... from UX perspective if want to offer a third option alongside the two other options (Standard, Large) it would be nice if we could not use a break line for the third option as all three break out of the container.

Unlike the editor options, which scale better and we also need to update soon, for the workspace class selection would be better if users had to choose through a linear list of options so that they feel like they are selecting from a range of increasingly better options, not just alternatives.

Ways forward:
1️⃣ Introduce a third option in a new line and improve the UX in future iterations.
2️⃣ Keep the vertical alignment but use narrower width, see screenshot below.
3️⃣ Introduce a more flexible component or pattern like a dropdown, see #13116 and relevant discussion (internal).

Early design for going with option 2️⃣
Screenshot 2022-11-28 at 7 15 10 PM

@atduarte atduarte changed the title Create an X-Large (16 cores, 32GB) workspace class Epic: Create an X-Large (16 cores, 32GB) workspace class Feb 10, 2023
@smiley9000
Copy link

what about 8v cpu 16gb memory and 320gb ssd

@TouchstoneTheDev
Copy link

TouchstoneTheDev commented Jul 18, 2023

what about 8v cpu 16gb memory and 320gb ssd

Hell yeah that will be awesome
We need it for llmops
320 gb would be overkill but gitpod can just give a thought on making storage big or think about it and adjust according to there

@SonicandTailsCD
Copy link

That's honestly too much, but understandable for high-end software.
I'd definitively want just 8 cores, 16GB of RAM and maybe like 128GB of /workspace?
Oh! And VNC support is amazing, I'm already trying it out :D
Just a thought tho, ignore this sh*tty ol' hedgehog if you want haha :)

Copy link
Contributor

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.

@github-actions github-actions bot added the meta: stale This issue/PR is stale and will be closed soon label May 22, 2024
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Jun 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature: workspace classes meta: stale This issue/PR is stale and will be closed soon needs visual design team: workspace Issue belongs to the Workspace team type: epic
Projects
No open projects
Status: No status
Development

No branches or pull requests

5 participants