Reduce memory usage of Workspace Success Criteria dashboard
Open
Nobody has claimed this yet.
meta: never-stale
- Dominant language
- TypeScript
- Stars
- 13.8k
- Forks
- 1.4k
- Avg merge
- 17h 58m
- Merged PRs (30d)
- 5
Description
The Workspace Success Criteria dashboard currently uses a lot of memory. See message in internal Slack thread for a description of why and for different ways to solve it.
This action was created from Incident 167 by Mads Hartmann, using incident.io 🔥
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 linked Slack thread and Incident 167 for the dashboard's memory symptoms and proposed solutions. Then inspect the Workspace Success Criteria dashboard and reproduce its memory usage; the work is done when the chosen solution reduces memory use without regressing the dashboard.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100