gitpod
gitpod copied to clipboard
Epic: Create an X-Large (16 cores, 32GB) workspace class
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
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️⃣ |
|---|
![]() |
what about 8v cpu 16gb memory and 320gb ssd
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
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 :)
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.
