[server] Monitor and optimize Workspace Start
Open
Nobody has claimed this yet.
aspect: performance
component: server
meta: never-stale
operations: observability
team: webapp
type: improvement
- Dominant language
- TypeScript
- Stars
- 13.8k
- Forks
- 1.4k
- Avg merge
- 17h 58m
- Merged PRs (30d)
- 5
Description
This ticket is about running an optimization cycle (harvesting the top 3 performance improvements) for the workspace startup times between user sends request with context URL and ws-manager receives workspace spec.
Ideally, we introduce some observability metrics for this as well, so we can continuously monitor this.
Could be even a great long-standing success-criteria.
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
Trace the server-side path from a user request containing a context URL to ws-manager receiving the workspace spec. Profile workspace startup, identify the top three performance improvements, and define observability metrics that continuously measure this interval.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- backend, observability, performance
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100