Running benchmarks during release
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- JavaScript
- Stars
- 4.4k
- Forks
- 675
- Avg merge
- 22h 29m
- Merged PRs (30d)
- 1
Description
We recently ran into some significant performance drop due to some changes in-between releases.
Our current microbenchmarks partially take a very long time but we could start evaluating what microbenchmarks we could run before we release a new version to detect significant performance drops early on.
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
The issue does not name specific files, benchmarks, tests, or entry points. Start by locating the existing microbenchmarks and release process, then determine which benchmarks can complete before a release and define how performance regressions should be detected.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- performance
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100