Explanation
Why the waste happens and who it affects.
Since billing is based on allocated vCPUs, memory, and storage - not usage - any misalignment between actual workload needs and provisioned capacity leads to unnecessary spend. Common causes include:
- Initial oversizing during launch that was never revisited
- Non-production environments with continuous uptime but minimal use
- Databases used intermittently (e.g., for nightly reports) but kept running 24/7 Without rightsizing or scheduling strategies, these instances generate ongoing cost with limited business value.
Billing model
The pricing dimensions that drive this cost.
Billed based on:
- vCPU and memory provisioned, priced per hour and charged for every second the instance is running
- Storage provisioned (per GB-month); IOPS and throughput are billed separately only for Hyperdisk Balanced storage, above its 3,000 IOPS and 140 MBps baseline
- Backups and network egress Charges accrue regardless of utilization levels; costs reflect provisioned capacity, not actual usage.
How to detect
5 checks to find it in your estate.
- Review CPU and memory utilization trends over a representative period
- Identify instances with consistently low usage relative to provisioned specs
- Separate instances with no connections or query activity at all: those are idle rather than oversized, and deleting or stopping them saves more than rightsizing
- Evaluate whether the environment (dev, test, QA) requires full-time availability
- Examine storage and IOPS usage to identify excessive disk allocation
How to fix
5 ways to remove the waste.
- Right-size vCPU and memory allocations based on actual performance needs
- Schedule automatic shutdown for non-production instances during off-hours
- Use Cloud SQL's stop/start capability for intermittent workloads (stopping suspends instance charges, but storage and IP address charges continue)
- Evaluate whether occasional-query workloads can move to a smaller instance, such as a shared-core machine type, or to a serverless database option
- Implement monitoring to trigger reviews when utilization stays below a threshold
Documentation
Vendor references for pricing and configuration.