Track performance changes in CI
- Dominant language
- Rust
- Stars
- 3.6k
- Forks
- 1.3k
- Avg merge
- 2d 18h
- Merged PRs (30d)
- 169
Description
**Is your feature request related to a problem or challenge? Please describe what you are trying to do.**
Add a system to track performance over time, using the repository's existing benchmarks. This will help ensure that no unwanted performance regressions are merged, and give more visibility on performance improvement work like https://github.com/apache/arrow-rs/issues/6107
**Describe the solution you'd like**
Use https://codspeed.io/ with a new workflow that runs on every PR and the `master` branch.
**Additional context**
I already installed CodSpeed on a fork of `arrow-rs`, and you can see what it looks like on a PR that improves performance (based on https://github.com/apache/arrow-rs/pull/6145):
https://github.com/CodSpeedHQ/arrow-rs/pull/51
https://codspeed.io/CodSpeedHQ/arrow-rs/branches/fork-6145-samuelcolvin/improve-like-regex
Thanks @samuelcolvin for validating the need
Contributor guide
Research direction
Start by locating the repository's existing benchmarks and the current CI workflow configuration. Review the CodSpeed examples linked in the issue and determine how a workflow should run on pull requests and the master branch. Done means CodSpeed tracks benchmark performance and reports changes for both trigger types without disrupting existing CI.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- ci-cd, performance
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100