Prepare continuous benchmarking
Open
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 182
- Forks
- 99
- Avg merge
- 2d 23h
- Merged PRs (30d)
- 8
Description
Objective
- Prevent/detect performance regression automatically
Requirements
- Detect performance regression in PR (CI is failed)
- Detect performance regression in main commits (CI is failed)
- Easy to maintain over correctness
- For example: We don't want to maintain our server even if GitHub hosted runner may not provide stable computation resource.
Nice to have
- Visualize performance trends
Contributor guide
No contributing guide indexed for this repository
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
No files, tests, or entry points are named. Start by surveying the repository's existing CI and benchmark setup, then determine how performance results can be compared for pull requests and main-branch commits. Done means regressions fail CI without requiring a self-hosted server; trend visualization is optional.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- ci-cd, performance
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100