Repository navigation
v1.4 — Loki memcached cache right-sizing
loki-best-practices — memcached cache right-sizing
New operational knowledge in the loki-best-practices skill:
- The
grafana/lokiHelm chart shipschunksCache.allocatedMemory: 8192and
resultsCache.allocatedMemory: 1024(MB). That number is both memcached's
-mflag and the pod's memory request and limit (≈allocatedMemory × 1.2Mi),
so the two caches reserve ~11Gi per cluster regardless of log volume — the
single biggest memory reservation in the namespace and a common scheduling blocker. - Fix: right-size to
chunksCache.allocatedMemory: 1024+resultsCache.allocatedMemory: 256
(~1.5Gi total) via a two-linehelm upgrade --reuse-values -foverlay; the memcached
-mand the podresourcesmove together.
Captured in section 2b. Deployment & configuration and added to the Most common
pitfalls list (now 8). Drawn from a real fleet incident — a 16Gi worker pinned at
89% MEM requests was almost entirely the Loki chunk-cache pod.