Prepare and setup first iteration of additional Chromium repo performance testing pipeline
After selecting Chromium as our highest percentile test repository target we should now proceed with prepping and setting it up in a regular performance pipeline. This is planned to be an additional pipeline to compliment the existing performance pipelines.
The tasks to do this can be broken down as follows:
- Start with one weekly pipeline on 50k with targeted Git Repository related tests as this is the area of challenge.
- Throughly test the new project to understand it's performance profile and confirm nothing external is impacting tests such as network bandwidth
- Collaborate with Gitaly team to determine what is actionable failures and set GPT targets accordingly once ability is added in GPT
- Decide on if additional pipelines are needed on different architecture size classes. Or if 50k pipeline is enough to start for this iteration.
- Raised agreed issues with Gitaly to start ball rolling.
Stretch:
- Seed the Chromium Repo with a large amount of Issues and MRs (50000 each based on real life data).
- These should be varied with different amounts of comments
- MRs specifically should be additionally varied with different commit and diffs to allow us to pick different size targets like we do currently
- MRs should not create new branches however and should be based on existing branches in the project
- Create a project export of the seeded repo for importing into various environments. This may require building the export tarball manually with
git bundle
, etc...
Edited by Grant Young