<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=28579) </details> <!--IssueSummary end--> We now have the QA E2E tests running regularly in a production-like environment with the Gitaly N+1 detector enabled: https://gitlab.com/gitlab-org/gitlab-ce/issues/57911 Once all the code that makes too many requests is fixed (or mitigated via ` allow_n_plus_1_calls` blocks), we'll need the ability to lower [the N+1 detector limit](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/lib/gitlab/gitaly_client.rb#L31), without having to make a code change. E.g., as an environment variable, or as a feature flag (perhaps replacing the [`gitaly_enforce_requests_limits`](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/lib/gitlab/gitaly_client.rb#L297), since that flag was added for the sake of the Gitaly N+1 E2E tests)