chore: add performance regression test infrastructure.
Open
chore
- Dominant language
- Java
- Stars
- 2k
- Forks
- 392
- Avg merge
- 11h 24m
- Merged PRs (30d)
- 36
Description
#4072 shows that performance can be seriously impacted by small changes.
Today, with our CI, we would not detect any serious performance regression.
Goal: add some performance regression test infrastructure, in Github Actions, Jenkins or elsewhere if appropriate.
Contributor guide
Research direction
Start by reviewing issue #4072 and the repository's current CI configuration. Define how performance regressions should be measured and detected, then choose an appropriate CI system; the work is done when the infrastructure reliably flags serious performance regressions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, java
- Domain
- ci-cd, performance, testing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100