Choose a storage option
The storage options available for your Cloud SQL instance depend on themachine series you choose. Todetermine which storage option is available for your instance's machine series,seeMachine series overview.
Cloud SQL supports the following storage types:
Google Cloud Hyperdisk Balanced
Cloud SQL uses the Hyperdisk Balanced storage option foritsN4 machine series . This storage type is an Google Cloud Hyperdisk offering.Hyperdisk is the latest generation of network block storage. Itoffers scalable, high-performance storage with comprehensive data persistenceand management capabilities. You can also enableautomatic storage increasewith this storage option to have Cloud SQLautomatically increase the storage for your instancewhen it falls below the threshold size.
HyperdiskBalanced provides customizable throughput and IOPS. For more information, seeAbout HyperdiskBalanced.
Hyperdisk Balanced sets default IOPS and throughput values andlimits based on your instance's configuration, which include the machine typeand storage capacity. Storage capacity limits the default value, and the machinetype sets the maximum value for both IOPS and throughput. You can modify thesevalues for your instance.
N4 machine series IOPS and throughput limits
The following table shows the minimum and maximum limits for IOPS and throughputfor each machine type in theN4 machine series based onits vCPUs:
Note: Read and write IOPs and throughput values are combined forHyperdisk Balanced.| vCPUs | Minimum IOPS | Minimum throughput (MiB/s) | Hyperdisk Balanced | Hyperdisk Balanced HA | ||
|---|---|---|---|---|---|---|
| Maximum IOPs | Maximum throughput | Maximum IOPs | Maximum throughput | |||
| 0-7 | 3,000 | 140 | 15,000 | 240 | 15,000 | 240 |
| 8-15 | 3,000 | 140 | 15,000 | 480 | 15,000 | 480 |
| 16-31 | 3,000 | 140 | 80,000 | 1,200 | 80,000 | 1,200 |
| 32-47 | 3,000 | 140 | 100,000 | 1,600 | 100,000 | 1,200 |
| 48+ | 3,000 | 140 | 160,000 | 2,400 | 100,000 | 1,200 |
The following table shows the default Google Cloud Hyperdisk Balanced IOPS andthroughput values based on the selected disk size:
| Disk size | Default IOPS | Default throughput |
|---|---|---|
| 20 - 256 GB | 4,000 | 170 |
| > 256 - 512 GB | 7,000 | 240 |
| > 512 GB - 1 TB | 10,000 | Minimum of 500 or maximum throughput of machine type |
| > 1 TB - 4 TB | Minimum of 16,000 or maximum IOPS for machine type | Minimum of 750 or maximum throughput of machine type |
| > 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 also setcustom IOPS and throughput whenusing Hyperdisk Balanced.
Hyperdisk Balanced custom IOPS and throughput
You can set custom IOPS and throughput levels for your Google Cloud HyperdiskBalanced and Google Cloud Hyperdisk Balanced High Availability volumes. The modifiedvalues must meet the following requirements:
IOPS
- Minimum: 3,000 IOPS
- Maximum: 500 IOPS per GB disk capacity, for a maximum of 160,000 forGoogle Cloud Hyperdisk Balanced and a maximum of 100,000 forGoogle Cloud Hyperdisk Balanced High Availability.
Throughput
- Minimum: 140 MiB/s
- Maximum: For Google Cloud Hyperdisk Balanced, the greater of 2,400 MiB/sor the provisioned IOPS divided by 4. For Google Cloud Hyperdisk BalancedHigh Availability, the greater of 1,200 MiB/s, or the provisioned IOPSdivided by 4.
Hyperdisk Balanced limitations
Consider the following limitations when using HyperdiskBalanced with your Cloud SQL instances:
- Hyperdisk Balanced only allows changes to capacity and disksize, twice every four hours. Data workloads needing more frequentincreases might result in extended periods of full storage and might impactperformance.
- Hyperdisk Balanced only allows changes to IOPS and throughputonce every four hours. Data workloads needing more frequentincreases might result in extended periods of full storage and might impactperformance.
Solid-state drive (SSD)
The solid-state drive (SSD) option is available for the general purposededicated core, the N2, and the memorized-optimized-N2 machine series.
The SSD storage option provides an efficient, cost-effective option for yourCloud SQL Cloud SQL Enterprise edition instances. Compared to ahard diskdrive, SSD is faster and provides more predictable performance. SSDoffers high write and read throughput, and maintains low latency for dataaccess. This makes it an excellent option for storing active data that requiresfrequent, low-latency access.
SSD is a Persistent Disk volumes offering that provides durable network storagedevices. It is suitable for enterprise applications and high-performancedatabases that require lower latency and more IOPS. For more information, seeAbout Persistent Disk.
Cloud SQL sets IOPS and throughput for SSD storage based on the machinetype and storage capacity you configure. You can't configure the values for IOPSand throughput.
N2 and Memory-optimized-N2 machine series IOPS and throughput limits
The following table shows the maximum values for IOPS and throughput (in MiB/s)for the SSD storage option based on the number of vCPUs for Cloud SQL Enterprise Plus editioninstances using theN2 machine series and thememory-optimized-N2 machineseries:
| vCPUs | Zonal | Regional | ||
|---|---|---|---|---|
| Maximum IOPs (read/write) | Maximum throughput (read/write) | Maximum IOPs (read/write) | Maximum throughput (read/write) | |
| 2 | 15,000 / 15,000 | 240 / 240 | 15,000 / 15,000 | 240 / 120 |
| 4 | 15,000 / 15,000 | 240 / 240 | 15,000 / 15,000 | 240 / 120 |
| 8 | 15,000 / 15,000 | 800 / 800 | 15,000 / 15,000 | 800 / 400 |
| 16 | 25,000 / 25,000 | 1,200 / 1,200 | 25,000 / 25,000 | 1,200 / 600 |
| 32 | 60,000 / 60,000 | 1,200 / 1,200 | 60,000 / 60,000 | 1,200 / 600 |
| 48 | 60,000 / 60,000 | 1,200 / 1,200 | 60,000 / 60,000 | 1,200 / 600 |
| 64 | 100,000 / 100,000 | 1,200 / 1,200 | 100,000 / 80,000 | 1,200 / 1,000 |
| 80 | 100,000 / 100,000 | 1,200 / 1,200 | 100,000 / 80,000 | 1,200 / 1,000 |
| 96 | 100,000 / 100,000 | 1,200 / 1,200 | 100,000 / 80,000 | 1,200 / 1,000 |
| 128 | 100,000 / 100,000 | 1,200 / 1,200 | 100,000 / 80,000 | 1,200 / 1,000 |
General purpose dedicated core IOPS and throughput limits
The following table shows the maximum values for IOPS and throughput for the SSDstorage option based on the number of vCPUs for the general purpose dedicatedcore machine series:
| vCPUs | Zonal | Regional | ||
|---|---|---|---|---|
| Maximum IOPs (read/write) | Maximum throughput (read/write) | Maximum IOPs (read/write) | Maximum throughput (read/write) | |
| 1 | 15,000 / 15,000 | 200 / 200 | 15,000 / 15,000 | 200 / 100 |
| 2-7 | 15,000 / 15,000 | 240 / 240 | 15,000 / 15,000 | 240 / 120 |
| 8-15 | 15,000 / 15,000 | 800 / 800 | 15,000 / 15,000 | 800 / 400 |
| 16-31 | 25,000 / 25,000 | 1,200 / 1,200 | 25,000 / 25,000 | 1,200 / 600 |
| 32-63 | 60,000 / 60,000 | 1,200 / 1,200 | 60,000 / 60,000 | 1,200 / 600 |
| 64+ | 100,000 / 100,000 | 1,200 / 1,200 | 100,000 / 80,000 | 1,200 / 1,000 |
What's next
- Create an instance
- Learn more about themachine seriesavailable in Cloud SQL.
Except as otherwise noted, the content of this page is licensed under theCreative Commons Attribution 4.0 License, and code samples are licensed under theApache 2.0 License. For details, see theGoogle Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2025-12-15 UTC.