f9b77f362f2a4f553b7c26b59848e382d1ad95b2
Drop requests to match observed peak usage and widen CPU limits for burst headroom (Burstable QoS). Backend, web, Postgres, and Dragonfly all had requests == limits pinned at defaults well above measured 7-day peaks. - backend: req 100m/128Mi -> 50m/64Mi, lim 100m/128Mi -> 200m/128Mi - web: req 100m/128Mi -> 50m/96Mi, lim 100m/128Mi -> 200m/128Mi - postgres (CNPG): req 50m/256Mi -> 15m/128Mi, lim 200m/512Mi -> 100m/256Mi - dragonfly: req 100m/128Mi -> 100m/72Mi, lim 100m/128Mi -> 150m/128Mi RAM limits unchanged where reasonable to preserve OOM protection; Dragonfly CPU request kept at 100m (peak 74m) but limit raised to avoid throttling under brief bursts.
Description
No description provided
Languages
Go
60.3%
Svelte
20.3%
Dart
11.1%
TypeScript
5%
PLpgSQL
1.1%
Other
2.1%