fix(acceptance): 纳入 API 数据库池容量门禁

高并发 Gemini 验收暴露两地 API 数据库池仍固定为 16，导致连接池满载、readiness 失败且压力曲线只监测 Worker，无法及时识别真实瓶颈。\n\n将容量档位的数据库连接池同步应用到 API，发布工具和生产清单保持同一配置；压力采样及日志门禁覆盖 API 与 Worker 四个连接池，并在失败时保留验收 JSON 报告。\n\n验证：bash -n、ShellCheck、kubectl kustomize、git diff --check。
2026-07-31 02:46:10 +08:00
parent 7a193934ed
commit 489208cef9
3 changed files with 77 additions and 40 deletions
@@ -53,7 +53,7 @@ spec:
            - name: AI_GATEWAY_ASYNC_QUEUE_WORKER_ENABLED
              value: "false"
            - name: AI_GATEWAY_DATABASE_MAX_CONNS
-              value: "16"
+              value: "32"
            - name: AI_GATEWAY_MEDIA_REQUEST_CONCURRENCY
              value: "16"
            - name: AI_GATEWAY_MEDIA_MATERIALIZATION_CONCURRENCY
@@ -182,7 +182,7 @@ spec:
            - name: AI_GATEWAY_ASYNC_QUEUE_WORKER_ENABLED
              value: "false"
            - name: AI_GATEWAY_DATABASE_MAX_CONNS
-              value: "16"
+              value: "32"
            - name: AI_GATEWAY_MEDIA_REQUEST_CONCURRENCY
              value: "16"
            - name: AI_GATEWAY_MEDIA_MATERIALIZATION_CONCURRENCY