-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Epic: Workspaces with higher CPU capacity for Pro+ customers #7487
Comments
I would like to add my 50 cents to this. Since I'm currently evaluating Gitpod for my company. Here are the things I would like to know when choosing a web-ide like Gitpod
|
Hey @BrandiATMuhkuh! Thanks for checking out Gitpod. Let me see if I can help you out here.
The specs for one workspace are the following:
This may change in the future.
You're able to use local VSCode, see the relevant docs here.
Yes! I'm unsure of your exact set-up but port-forwarding does work. It's worth giving it a go, spinning up a workspace and if there's anything specific that doesn't work... Let us know and we'll try and help you out! If you're not aware, we also have a Discord community server where most of us hang out. Feel free to drop by as you set up Gitpod, we'd be more than happy to help. |
Summary
We aim to mitigate issues that current paying customers are having with longer building/testing times, by providing all Professional and Unleashed customers with workspaces that have more CPU resources. This is to be achieved by running the workspaces in separate clusters where workspace density is cut in half.
Context
Professional SaaS customers are experiencing slower building and testing times in Gitpod than locally due to lack of CPU capacity. We want to mitigate this issue asap, and therefore will focus only on the CPU capacity and follow an iterative MVC approach.
Original RFC
Value
Resolving an immediate and major problem that some of our customers are facing.
Acceptance criteria
Measurement
Growth Area
Adoption & Retention
Persona(s)
Teams serious about wanting to adopt Gitpod SaaS
Hypothesis
Open Questions
Issues
The text was updated successfully, but these errors were encountered: