Storage options overview

MySQL  |  PostgreSQL  |  SQL Server

This page describes the different storage types available for yourCloud SQL instances.

Cloud SQL offers different storage type options depending on theCloud 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 theC4A machine series.
  • Performance Persistent Disk (SSD): a persistent disk offering forhigh-performance databases and is backed bysolid-state drives. This storage type is available for the Cloud SQL Enterprise editionmachine series, and the Cloud SQL Enterprise Plus edition N2 machine series.

For more information about the different machine series and types availablefor Cloud SQL, seeMachine series overview.

Google Cloud Hyperdisk Balanced

Preview — Hyperdisk Balanced storage

This feature is subject to the "Pre-GA Offerings Terms" in the General Service Terms section of theService Specific Terms. You can process personal data for this feature as outlined in theCloud Data Processing Addendum, subject to the obligations and restrictions described in the agreement under which you access Google Cloud. Pre-GA features are available "as is" and might have limited support. For more information, see thelaunch stage descriptions.

Cloud SQL uses the Hyperdisk Balanced storage option for itsC4A machine series.This storage type is a Google Cloud Hyperdisk offering. Hyperdisk is thenewest generation of network block storage service. It offersscalable, high-performance storage service with a comprehensive suiteof data persistence and management capabilities. Hyperdisk Balanced providescustomizable throughput and IOPS. For moreinformation, seeAbout Hyperdisk Balanced.

Default values and limits

Default values and limits for IOPS and throughput for Hyperdisk Balanced areset based on your instance's configuration, specifically the machine type andstorage capacity. The selected storage capacity limits the default value andthe machine type sets the maximum value for both IOPS and throughput. You canmodify these values for your instance at any time.

The following table shows the minimum and maximum limits for IOPS and throughputfor each machine type in theC4A machine series based onits vCPUs:

vCPUsMinimum IOPSMinimum throughput (MiB/s)Hyperdisk BalancedHyperdisk Balanced HA
Maximum IOPsMaximum throughput (MiB/s)Maximum IOPsMaximum throughput (MiB/s)
23,00014050,00080050,000800
43,00014050,00080050,000800
83,00014050,0001,00050,0001,000
163,00014080,0001,60080,0001,200
323,000140120,0002,400100,0001,200
483,000140160,0002,400100,0001,200
643,000140160,0002,400100,0001,200
723,000140160,0002,400100,0001,200

The following table shows the default Google Cloud Hyperdisk BalancedIOPS and throughput values based on the selected disk size:

Disk sizeDefault IOPSDefault throughput (MiB/s)
20 - 256 GB4,000170
> 256 - 512 GB7,000240
> 512 GB - 1 TB10,000500
> 1 TB - 4 TB16,000750
> 4 TB - 32 TBMinimum of 70,000 or maximum IOPS for machine typeMinimum of 1,200 or maximum throughput for machine type
> 32 TB - 64 TBMinimum of 100,000 or maximum IOPS for machine typeMinimum of 1,200 or maximum throughput for machine type

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 Hyperdisk Balanced with yourCloud SQL instances:

  • Hyperdisk Balanced only allows changes to capacity, IOPS, and throughputonce every four hours. Data workloads needing more frequent increases mightresult in extended periods of full storage and might impact performance.

Performance Persistent Disk

Cloud SQL uses the Performance Persistent Disk (SSD) storage option forits N2 machine series. SSD is aPersistent Disk volumes offering that provides durable network storage devices andis suitable for enterprise applications and high-performance databases thatrequire lower latency and more IOPS.For more information, seeAbout Persistent Disk.

IOPs and throughput for SSD storage type are set based on the machine typeand storage capacity you set. You can't configure the values for IOPS andthroughput.

N2 SSD IOPS and throughput limits

The following table shows the maximum values for IOPS and throughputfor the SSD storage option based on the number of vCPUs for theN2 machine series:

vCPUsMaximum write IOPSMaximum read IOPSMaximum write throughput (MiB/s)Maximum read throughput (MiB/s)
215,00015,000240240
415,00015,000240240
815,00015,000800800
1625,00025,0001,0001,200
3260,00060,0001,0001,200
4860,00060,0001,0001,200
6480,00060,0001,0001,200
8080,00060,0001,0001,200
9680,00060,0001,0001,200
12880,00060,0001,0001,200
Note: To increase the IOPS and throughput values for the N2 machine series,increase the storage capacity of your instance.

What's next

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-07-14 UTC.