This page covers the storage options supported by Cloud SQL, and some key considerations for selecting the storage option that best fits your instance's needs.
The storage options available for your Cloud SQL instance depend on the machine series you choose. To find which storage option is available for your instance's machine series, see Machine series availability.
Cloud SQL supports the following storage types:
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. 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 customizable throughput and IOPS. For more information, see About Hyperdisk Balanced.
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 (MiB/s) | Hyperdisk Balanced | Hyperdisk Balanced HA | ||
|---|---|---|---|---|---|---|
| Maximum IOPs | Maximum throughput (MiB/s) | Maximum IOPs | Maximum throughput (MiB/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 (MiB/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 MiB/s
- Maximum: For Google Cloud Hyperdisk Balanced, the greater of 2,400 MiB/s or the provisioned IOPS divided by 4. For Google Cloud Hyperdisk Balanced High Availability, the greater of 1,200 MiB/s, 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.
Solid-state drive (SSD)
The solid-state drive (SSD) option is available for Cloud SQL Enterprise edition instances and Cloud SQL Enterprise Plus edition instances using the N2 machine series only.
The SSD storage option provides an efficient and cost-effective option for your Cloud SQL Cloud SQL Enterprise edition instances. When compared to a hard disk drive, SSD is faster and brings more predictable performance. SSD has high write and read throughput, and maintains low latency with data access. This makes it a great option to store active data that requires frequent and low-latency access.
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.
Cloud SQL Enterprise Plus edition 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 Cloud SQL Enterprise Plus edition instances using the [N2 machine series](/sql/docs/mysql/machine-series-overview#n2):
| vCPUs | Maximum read IOPS | Maximum write IOPS | Maximum read throughput (MiB/s) | Maximum write throughput (MiB/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,200 | 1,200 |
| 32 | 60,000 | 60,000 | 1,200 | 1,200 |
| 48 | 60,000 | 60,000 | 1,200 | 1,200 |
| 64 | 60,000 | 80,000 | 1,200 | 1,200 |
| 80 | 60,000 | 80,000 | 1,200 | 1,200 |
| 96 | 60,000 | 80,000 | 1,200 | 1,200 |
| 128 | 60,000 | 80,000 | 1,200 | 1,200 |
Cloud SQL Enterprise edition 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 Cloud SQL Enterprise edition instances:
| vCPUs | Maximum read IOPS | Maximum write IOPS | Maximum read throughput (MiB/s) | Maximum write throughput (MiB/s) |
|---|---|---|---|---|
| 1 | 15,000 | 15,000 | 200 | 200 |
| 2-7 | 15,000 | 15,000 | 240 | 240 |
| 8-15 | 15,000 | 15,000 | 800 | 800 |
| 16-31 | 25,000 | 25,000 | 1,200 | 1,200 |
| 32-63 | 60,000 | 60,000 | 1,200 | 1,200 |
| 64+ | 100,000 | 100,000 | 1,200 | 1,200 |
Hard disk drive (HDD)
The hard disk drive (HDD) storage option is available for Cloud SQL Enterprise edition instances only, and might be an appropriate choice in certain use cases. Some use cases include instances with large datasets (>10 TB) that aren't latency-sensitive, are accessed infrequently, or if the cost of storage is an important consideration. HDD might also be suitable if your workload falls into one of the following categories:
- Batch workloads with scans and writes, and no more than occasional random reads of a few rows.
- Data archival, where you write large amounts of data and rarely read that data.
For example, if you plan to store extensive historical data for a large number of remote-sensing devices and then use the data to generate daily reports, then the cost savings for HDD storage might justify the performance trade-off. However, if you plan to use the data to display a real-time dashboard, then HDD might not be the optimal choice because reads are much more frequent in this case, and reads are much slower with HDD storage.
HDD IOPS and throughput limits
The following table shows the maximum values for IOPS and throughput for the HDD storage option based on the number of vCPUs for Cloud SQL instances:
| vCPUs | Maximum read IOPS | Maximum write IOPS | Maximum read throughput (MiB/s) | Maximum write throughput (MiB/s) |
|---|---|---|---|---|
| 1 | 1,000 | 10,000 | 200 | 200 |
| 2-7 | 3,000 | 15,000 | 240 | 240 |
| 8-15 | 5,000 | 15,000 | 800 | 400 |
| 16+ | 7,500 | 15,000 | 1,200 | 400 |
What's next
- Create an instance
- Learn more about the different machine series available in Cloud SQL.