Run prebuilds in the storage-bucket's region
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 13.8k
- Forks
- 1.4k
- Avg merge
- 17h 58m
- Merged PRs (30d)
- 5
Description
Running a prebuild in the same geographical region of the storage bucket to which the prebuild will be uploaded saves us costs in two places:
- for all prebuilds, the compute egress costs from uploading the completed prebuild to its bucket.
- for incremental prebuilds, the storage egress of downloading a prebuild with the intention of updating it.
proposed solution: ws-manager-bridge/server should be aware of the geographical region of the prebuild's storage bucket and route the prebuild to a workspace cluster in the same region.
While we may not have capacity to fix this immediately it would be great to have this on the radar.
Related:
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
Start by reading the ws-manager-bridge/server prebuild routing path and the related issues linked in the report. Determine how the storage bucket's geographical region can be obtained and how workspace clusters are selected; done means prebuilds are routed to a cluster in the bucket's region, including incremental prebuilds.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- backend, cloud, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100