Redis

Peak Memory Exceeded Indicates Historical Capacity Issues

info
Resource ContentionUpdated Mar 2, 2026

When redis.memory.peak significantly exceeds redis.memory.used, the system has experienced memory pressure in the past that may recur. This indicates need for capacity planning or workload pattern investigation.

Technologies:
How to detect:

Monitor redis.memory.peak > redis.memory.used * 1.3 sustained over time. Large gap indicates historical peak usage significantly higher than current. Correlate with redis.memory.maxmemory to determine if past peaks approached limits. Track over days/weeks to identify usage patterns.

Recommended action:

Investigate workload patterns that caused peak usage. Review logs and application metrics from peak timestamp. Assess if peak usage will recur (daily/weekly patterns). Consider increasing maxmemory or provisioning headroom if peaks are routine. Use memory analysis commands (MEMORY DOCTOR, MEMORY STATS) to understand memory composition. Implement alerting before reaching previous peak levels.