Explore if the performance of Git Push over HTTPs under load can be improved to meet target
The TTFB P90 of Git Push over HTTPs is over the main target of 200ms:
* Environment: 10k
* Environment Version: 14.1.0-pre `669b47122f4`
* Option: 60s_200rps
* Date: 2021-06-23
* Run Time: 1h 25m 3.31s (Start: 04:36:33 UTC, End: 06:01:36 UTC)
* GPT Version: v2.8.0
NAME | RPS | RPS RESULT | TTFB AVG | TTFB P90 | REQ STATUS | RESULT
---------------------------|-------|----------------------|-----------|-----------------------|----------------|-------
git_push | 4/s | 3.59/s (>3.20/s) | 372.22ms | 535.00ms (<1000ms) | 100.00% (>99%) | Passed
These were tested against gitlabhq
project. The example url of the request on Staging can be found at Current Test Details
page by the test name.
Please see Git Push over HTTPS for the more information on how the test is configured.
The GPT results can be found at https://gitlab.com/gitlab-org/quality/performance/-/wikis/Benchmarks/Latest/10k or GPT Test results Grafana dashboard.
As per our performance targets the controller action is above our main target of 200ms and fall under the severity4 tier. Task is to explore if there is a way to improve performance to meet the target.
Steps to reproduce
- Check out the GitLab Performance Tool
- Run the specific test with the
run-k6
command. For example against the 10k environment you would run this following from the project root:./run-k6 -e environments/10k.json -o 60s_200rps.json -t api_v4_projects_issues.js
. You will need an ACCESS_TOKEN for this endpoint as well. - If you're seeking to run the test against your own environment the Tool's documentation has details on how to achieve this.