PERF(resources): remove CPU limits - keep memory limits only

- CPU throttling prevents app startup, not crashes
- Memory OOM is the real cascading failure cause
- CPU request ensures fair scheduling
This commit is contained in:
2026-01-07 23:48:47 +09:00
parent 6af1964495
commit 35df7aa64e
6 changed files with 15 additions and 13 deletions

View File

@@ -13,11 +13,10 @@ replicaCount: 1
# Resource requests for operator
resources:
requests:
cpu: 5m # Reduced from 100m based on actual usage (2m)
cpu: 15m
memory: 128Mi
limits:
# cpu: removed to prevent throttling
memory: 512Mi
memory: 192Mi
# RBAC
rbac:

View File

@@ -35,8 +35,10 @@ rootPasswordSecretKey: root-password
# Resources
resources:
requests:
memory: 512Mi
cpu: 5m # Reduced from 30m based on actual usage (1-2m)
memory: 263Mi
cpu: 15m
limits:
memory: 263Mi
# Service
service:

View File

@@ -21,8 +21,10 @@ controllers:
key: database-url
resources:
requests:
cpu: 5m
memory: 64Mi
cpu: 15m
memory: 100Mi
limits:
memory: 150Mi
probes:
liveness:
enabled: true

View File

@@ -21,8 +21,8 @@ spec:
memory: "256Mi"
cpu: "30m"
limits:
memory: "512Mi"
# cpu: no limit to prevent throttling
memory: "384Mi"
cpu: "45m"
# PostgreSQL configuration
postgresql:

View File

@@ -16,8 +16,7 @@ resources:
cpu: 50m
memory: 128Mi
limits:
# cpu: removed to prevent throttling
memory: 512Mi
memory: 192Mi
# Init containers for plugins
initContainers:

View File

@@ -30,10 +30,10 @@ controllers:
periodSeconds: 10
resources:
requests:
cpu: 10m
cpu: 15m
memory: 128Mi
limits:
memory: 512Mi
memory: 192Mi
pod:
tolerations:
- key: "node-role.kubernetes.io/master"