Improve performance of Project Merge Requests API under load into next tier
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
The TTFB (Time to First Byte) of the Project Merge Requests API is slightly over our performance target under load:
* Environment: 25k
* Environment Version: 17.11.0-pre `fd3e40cbbcf`
* Option: 60s_500rps
* Date: 2025-03-24
* Run Time: 1h 35m 24.77s (Start: 04:54:20 UTC, End: 06:29:45 UTC)
* GPT Version: v2.15.0
NAME | RPS | RPS RESULT | TTFB AVG | TTFB P90 | REQ STATUS | RESULT
---------------------------------------------------------|-------|----------------------|-----------|-----------------------|----------------|---------
api_v4_projects_merge_requests | 500/s | 492.55/s (>400.00/s) | 184.79ms | 233.45ms (<200ms) | 100.00% (>99%) | FAILED²
In other environments like 10k, the failures are less common:
Test Details
Testing was done on our 10k Reference Architecture environment with our lab condition GitLab Performance Tool pipeline. The project being tested is a copy of gitlabhq (tarball can be found here). GitLab Performance Tool tests information is listed at Current test details page.
The latest GitLab Performance pipeline results can always be found here. Through this page full Server Metrics can be found via the Metrics Dashboard link on that page.
As per our performance targets this endpoint's TTFB metric is above the target of 200 ms which is severity4. Task is to improve the endpoint's performance into next tier.