Epic: Performance metrics/milestones for profiling and optimisation of workspace loading
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 13.8k
- Forks
- 1.4k
- Avg merge
- 17h 58m
- Merged PRs (30d)
- 5
Description
Often users ask us about performance issues, however Gitpod has many aspects that load when a workpace loads:
- Fetching of base image
- Starting workspace
- Starting IDE
- Starting terminal processess etc
However, there is no holistic way for a user or operator of Gitpod to optimise their setup across these phases. Additionally, there is currently no way to get visibility into a workspace performance issue if the workspace itself is unresponsive.
Relates to:
- https://github.com/gitpod-io/gitpod/issues/10802
- https://github.com/gitpod-io/website/issues/2246
- https://github.com/gitpod-io/gitpod/issues/3738
- https://github.com/gitpod-io/gitpod/issues/9994
This epic would be to:
- Define these key "loading" milestones in Gitpod (end-to-end)
- Expose this information somewhere to the user so they can: debug + optimise their Gitpod workspace loading
(internal info)
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 reviewing the linked issues 10802, 2246, 3738, and 9994, plus the internal customer issue 69, to understand the existing performance concerns. Define the end-to-end workspace-loading milestones and where users or operators should see them; done requires an agreed holistic profiling and optimisation path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- cloud, observability, performance
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100