This page describes the different storage types available for your Cloud SQL instances.
Cloud SQL offers different storage type options depending on the Cloud SQL edition and the machine series you select for your instance:
- Hyperdisk Balanced (Preview): a Google Cloud Hyperdisk offering that offers scalable, high-performance storage service. This storage type is only available for the C4A machine series.
- Performance Persistent Disk (SSD): a persistent disk offering for high-performance databases and is backed by solid-state drives. This storage type is available for the Cloud SQL Enterprise Plus edition machine series, and the Cloud SQL Enterprise edition N2 machine series.
For more information about the different machine series and types available for Cloud SQL, see Machine series overview.
Google Cloud Hyperdisk Balanced
Cloud SQL uses the Hyperdisk Balanced storage option for its C4A machine series. This storage type is a Google Cloud Hyperdisk offering. Google Cloud Hyperdisk is the newest generation of network block storage service. It offers scalable, high-performance storage service with a comprehensive suite of data persistence and management capabilities. Hyperdisk Balanced provides a customizable throughput and IOPs. For more information, see About Google Cloud Hyperdisk.
Default values and limits
Default values and limits for IOPS and throughput for Hyperdisk Balanced are set based on your instance's configuration, specifically the machine type and storage capacity. The selected storage capacity limits the default value and the machine type sets the maximum value for both IOPS and throughput. You can modify these values for your instance at any time.
The following table shows the minimum and maximum limits for IOPS and throughput for each machine type in the C4A machine series based on its vCPUs:
| vCPUs | Minimum IOPS | Minimum throughput (MB/s) | Hyperdisk Balanced | Hyperdisk Balanced HA | ||
|---|---|---|---|---|---|---|
| Maximum IOPs | Maximum throughput (MB/s) | Maximum IOPs | Maximum throughput (MB/s) | |||
| 2 | 3,000 | 140 | 50,000 | 800 | 50,000 | 800 |
| 4 | 3,000 | 140 | 50,000 | 800 | 50,000 | 800 |
| 8 | 3,000 | 140 | 50,000 | 1,000 | 50,000 | 1,000 |
| 16 | 3,000 | 140 | 80,000 | 1,600 | 80,000 | 1,200 |
| 32 | 3,000 | 140 | 120,000 | 2,400 | 100,000 | 1,200 |
| 48 | 3,000 | 140 | 160,000 | 2,400 | 100,000 | 1,200 |
| 64 | 3,000 | 140 | 160,000 | 2,400 | 100,000 | 1,200 |
| 72 | 3,000 | 140 | 160,000 | 2,400 | 100,000 | 1,200 |
The following table shows the default Google Cloud Hyperdisk Balanced IOPS and throughput values based on the selected disk size:
| Disk size | Default IOPS | Default throughput (MB/s) |
|---|---|---|
| 20 - 256 GB | 4,000 | 170 |
| > 256 - 512 GB | 7,000 | 240 |
| > 512 GB - 1 TB | 10,000 | 500 |
| > 1 TB - 4 TB | 16,000 | 750 |
| > 4 TB - 32 TB | Minimum of 70,000 or maximum IOPS for machine type | Minimum of 1,200 or maximum throughput for machine type |
| > 32 TB - 64 TB | Minimum of 100,000 or maximum IOPS for machine type | Minimum of 1,200 or maximum throughput for machine type |
You can set custom IOPS and throughput levels for your Google Cloud Hyperdisk Balanced and Google Cloud Hyperdisk balanced high availability volumes. The modified values must meet the following requirements:
IOPS
- Minimum: 3,000 IOPS
- Maximum: 500 IOPS per GB disk capacity, for a maximum of 160,000 for Google Cloud Hyperdisk Balanced and a maximum of 100,000 for Google Cloud Hyperdisk Balanced high availability.
Throughput
- Minimum: 140 MBps
- Maximum: For Google Cloud Hyperdisk Balanced, the greater of 2,400 MBps or the provisioned IOPS divided by 4. For Google Cloud Hyperdisk Balanced high availability, the greater of 1,200 MBps, or the provisioned IOPS divided by 4.
Hyperdisk Balanced limitations
Consider the following limitations when using Hyperdisk Balanced with your Cloud SQL instances:
- Hyperdisk Balanced only allows changes to capacity, IOPS, and throughput once every four hours. Data workloads needing more frequent increases might result in extended periods of full storage and might impact performance.
Performance Persistent Disk
Cloud SQL uses the Performance Persistent Disk (SSD) storage option for its N2 machine series. SSD is a Persistent Disk volumes offering that provides durable network storage devices and is suitable for enterprise applications and high-performance databases that require lower latency and more IOPS. For more information, see About Persistent Disk.
IOPs and throughput for SSD storage type are set based on the machine type and storage capacity you set. You can't configure the values for IOPS and throughput.
N2 SSD IOPS and throughput limits
The following table shows the maximum values for IOPS and throughput for the SSD storage option based on the number of vCPUs for the N2 machine series:
| vCPUs | Maximum write IOPS | Maximum read IOPS | Maximum write throughput (MB/s) | Maximum read throughput (MB/s) |
|---|---|---|---|---|
| 2 | 15,000 | 15,000 | 240 | 240 |
| 4 | 15,000 | 15,000 | 240 | 240 |
| 8 | 15,000 | 15,000 | 800 | 800 |
| 16 | 25,000 | 25,000 | 1,000 | 1,200 |
| 32 | 60,000 | 60,000 | 1,000 | 1,200 |
| 48 | 60,000 | 60,000 | 1,000 | 1,200 |
| 64 | 80,000 | 60,000 | 1,000 | 1,200 |
| 80 | 80,000 | 60,000 | 1,000 | 1,200 |
| 96 | 80,000 | 60,000 | 1,000 | 1,200 |
| 128 | 80,000 | 60,000 | 1,000 | 1,200 |
What's next
- Create an instance
- Learn more about the different machine series available in Cloud SQL.