Explanation
Why the waste happens and who it affects.
In test environments, migration scenarios, or deprecated application components, Redis instances are often left running unintentionally. Since Redis does not autoscale or suspend, unused capacity results in 100% waste until explicitly deleted.
Billing model
The pricing dimensions that drive this cost.
Billed based on:
- Provisioned instance size (memory capacity)
- Instance tier (Standard or Basic)
- Uptime (per second billing). Costs accrue regardless of actual data stored or traffic served.
How to detect
5 checks to find it in your estate.
- Review memory usage and operation count metrics over a recent period
- Identify instances with zero or near-zero read/write commands
- Check for stale endpoints not referenced in active application code or configuration
- Validate whether the instance serves any production dependencies
- Confirm environment tags (e.g., dev, staging) that may indicate non-critical usage
How to fix
4 ways to remove the waste.
- Decommission idle Redis instances no longer in use
- Consider scaling down instance size if usage is expected to remain minimal
- Use labels to track instance ownership and business purpose for easier future audits
- Establish a periodic review process to catch long-idle memory store resources
Documentation
Vendor references for pricing and configuration.
https://cloud.google.com/memorystore/docs/redis/pricing https://cloud.google.com/memorystore/docs/redis/monitoring-metrics https://cloud.google.com/memorystore/docs/redis/creating-managing-instances