Set up benchmarking in CI
Open
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 197
- Forks
- 32
- PR merge metrics
- No merged PRs in 30d
Description
We should benchmark roofer as part of our CI to spot performance regressions. However, GH Actions is not suitable for benchmarking by default, but this post explain how could we still use it.
The alternative would be to connect GH to one of our servers and run the benchmarks there.
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
No files, tests, workflows, or benchmark entry points are named in the issue. Start by reading the linked GitHub Actions benchmarking post and inspecting the repository's existing CI and benchmark setup. Decide whether benchmarks should run in GitHub Actions or on a connected server, then document a reproducible regression-detection workflow.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, github-actions
- Domain
- ci-cd, performance, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100