-
Notifications
You must be signed in to change notification settings - Fork 28
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
Write RFC around performance/caching improvements #128
Comments
Status update: We've written an RFC (Notion: Improving Workspace Startup Performance with Envbuilder), but we're still investigating the best path forward. For now, we've decided to create two PoCs to validate our approach:
If we can prove these two methods work, we will be able to implement our ideal solution, and have options for further improvement. (Moving this issue to blocked until validation is complete.) |
Both #185 and #186 have now been investigated and the approach for utilizing pre-built images has been validated. (See conclusions in aforementioned issues.) See #213 for a reference implementation combining these PoCs. The updated RFC is still pending approval, but in broad strokes we're looking to implement the following key components:
(The details for each component have been omitted for brevity and pending approval.) |
Thanks for the update, Mathias. I will make sure to include the relevant issues in the current sprint. |
We want to re-architect envbuilder in a way where it can run inside an existing devcontainer image (
registry.company.com/envbuilder-images/python-project:latest
) and pick up and rebuild any stale layers. This also includes a Terraform data source where it can check if there is an existing registry image for a repo/branch/Dockerfile or if the bare envbuilder image needs to be started. Envbuilder will also push the newly-built imageThe text was updated successfully, but these errors were encountered: