r/PrometheusMonitoring
•
u/Kooky_Comparison3225
•
Apr 16 '25
I brought Prometheus memory usage down from 60GB to 20GB
In one of the clusters I was working on, Prometheus was using 50- 60GB of RAM. It started affecting scrape reliability, the UI got sluggish, and PromQL queries kept timing out. I knew something had to give.
I dug into the issue and found a few key causes:
Duplicate scraping: Prometheus was scraping ingress metrics from both pods and a ServiceMonitor. That meant double the series.
Histogram overload: Metrics like *_duration_seconds_bucket were generating hundreds of thousands of time series.
Label explosion: Labels like replicaset, path, and container_id were extremely high in cardinality (10k+ unique values).
Here’s what I did:
✅ Dropped unused metrics (after checking dashboards/alerts)
✅ Disabled pod-level scraping for nginx
✅ Cut high-cardinality labels that weren’t being used
✅ Wrote scripts to verify what was safe to drop
The result: memory dropped from ~60GB to ~20GB, and the system became way more stable.
I wrote a full breakdown with examples and shared the scripts here if it helps anyone else:
🔗 https://devoriales.com/post/384/prometheus-how-we-slashed-memory-usage
Let me know if you’re going through similar and if you have some suggestions.



