From 60672212bf72e4ba5c4b50122cbdbc4f5b464a1f Mon Sep 17 00:00:00 2001
From: Zack <zack@futo.org>
Date: Wed, 8 Apr 2026 12:53:57 +0100
Subject: [PATCH] fix: tune vmsingle resource limits and query settings

- remove explicit search.maxUniqueTimeseries cap (600k) to let vm auto-calculate (~4.3m with 32gi)
- add search.logSlowQueryDuration for query observability
- bump vmsingle memory from 8gi to 32gi with proper requests
- add cpu/memory requests for both vmsingle and vmagent
- remove cpu limit on vmsingle to allow unbounded burst
---
 .../monitoring/victoria-metrics/app/helmrelease.yaml   | 10 ++++++++--
 1 file changed, 8 insertions(+), 2 deletions(-)

diff --git a/kubernetes/apps/monitoring/victoria-metrics/app/helmrelease.yaml b/kubernetes/apps/monitoring/victoria-metrics/app/helmrelease.yaml
index 812811a1d..d15577a9b 100644
--- a/kubernetes/apps/monitoring/victoria-metrics/app/helmrelease.yaml
+++ b/kubernetes/apps/monitoring/victoria-metrics/app/helmrelease.yaml
@@ -47,13 +47,19 @@ spec:
     vmsingle:
       spec:
         extraArgs:
-          search.maxUniqueTimeseries: "600000"
+          search.logSlowQueryDuration: "3s"
         resources:
+          requests:
+            cpu: 2000m
+            memory: 32Gi
           limits:
-            memory: 8Gi
+            memory: 32Gi
     vmagent:
       spec:
         resources:
+          requests:
+            cpu: 500m
+            memory: 512Mi
           limits:
             cpu: 2000m
             memory: 1Gi