Epic: Prebuilds only available in user-specified regions
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 13.8k
- Forks
- 1.4k
- Avg merge
- 17h 58m
- Merged PRs (30d)
- 5
Description
Context
At the moment, prebuilds run in the US region which means that whenever someone starts a workspace in a different region, they must be transferred across continents. This results in slower workspace startup times and poor cost effectiveness.
The problem will be exacerbated as soon as we launch https://github.com/gitpod-io/gitpod/issues/7489.
Goal
Improve workspace startup times and cost effectiveness.
Proposed solution
Only allow prebuilds to be used in the regions that they were computed and stored, and require users to specify what regions those should be for each project. When nothing is specified, the prebuild will be computed, stored and usable only in the default user's region.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are identified. Start by locating the prebuild workflow and the existing region-selection and storage logic; define how project region configuration and the default user region should affect computation, storage, and reuse, then verify startup behavior across regions.
Written by the indexing model from the issue text.
Assessment
- Domain
- cloud
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100