From fa23e5084c545c5540d357214ad1164f9028b6a2 Mon Sep 17 00:00:00 2001
From: Scooby Husky <garrettstone499@gmail.com>
Date: Sun, 15 Mar 2026 22:47:39 -0500
Subject: [PATCH] Reduce GitLab latency: increase Gitaly CPU limit and Puma
 workers

Gitaly CPU limit was 250m causing throttling on git operations (485ms
p99 to webservice). Increased to 1 core with 100m request. Also added
workerProcesses: 3 to webservice for better request concurrency
(was default 2).

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
---
 apps/gitlab/values.yaml | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/apps/gitlab/values.yaml b/apps/gitlab/values.yaml
index d6032c3..954d1ef 100644
--- a/apps/gitlab/values.yaml
+++ b/apps/gitlab/values.yaml
@@ -155,6 +155,7 @@ gitlab:
   webservice:
     minReplicas: 2
     maxReplicas: 3
+    workerProcesses: 3
 
     # Note: hostAliases for OIDC SSL validation are applied via helmfile postsync hook
     # (GitLab chart doesn't support hostAliases in values.yaml)
@@ -256,10 +257,10 @@ gitlab:
     # Production resources
     resources:
       requests:
-        cpu: 50m
+        cpu: 100m
         memory: 512Mi
       limits:
-        cpu: 250m
+        cpu: "1"
         memory: 2Gi
   
   # GitLab Runner - enabled for CI/CD