This document lists the performance limits for machine types that supportGoogle Cloud Hyperdisk. For a detailed discussion of how Hyperdiskperformance works, seeAbout Hyperdisk performance.

For Persistent Disk performance limits, seePerformance limits by machine type for Persistent Disk.

In this document, machine types are denoted in this format:M-*-N, where:

• M is the machine series, for example,C3
• * represents all memory and CPU configurations, for example,standard orhighcpu
• N is the number of vCPUs, CPUs, or the GPU designation, for example, 22 for an instance with 22 vCPUs, or8g for an instance with 8 GPUs

This format includes the following machine types, wherever available:

• bare metal machine types (*-metal)
• machine types that come with attached Local SSD disks (*-lssd,*-standardlssd, or*-highlssd).

For example,c3-*-176 refers to all C3 machine types with 176 vCPUs, namelyc3-standard-176,c3-highcpu-176,c3-highmem-176, andc3-standard-176-lssd. For more information, seeCompute Engine terminology.

Determine which limits apply

The performance limit that applies to your scenario depends on the instance'smachine type, and the number and type of Hyperdisk volumes youattached to the instance.

Choose from the following scenarios to determine which limits to consult.

• You're using multiple Hyperdisk types with the same instanceand you want to know the maximum performance for all the disks attachedto the instance.

  For example, suppose you have one Hyperdisk Balanced volume and two Hyperdisk Throughput volumes attachedto ac3-standard-22 virtual machine (VM) instance. The applicable performancelimits are listed in thePerformance limits by machine typesection of this document.

• You attached one or more Hyperdisk volumes of thesame type to an instance and you want to know the maximum performance all thevolumes can reach.

  For example, you have 3 Hyperdisk Balanced volumes attached to ac3-standard-22 VM.The applicable performance limits for the 3 volumes are listed in thePerformance limits by Hyperdisk typesection of this document.

Performance limits by machine type

If you use different Hyperdisk types with a single instance,the following table lists the maximum performance you can expect. This limitis shared among all Hyperdisk and, if supported, Persistent Diskvolumes attached to the instance.To learn more about how these limits work, seeHow instance performance limits affect performance.

The performance limits also apply tocustom N2, N2D, N4, N4A, and N4D machine types.

Select a machine series to display the performance limits for its machine types.

¹Also offers steady state performance. For these limits, seePerformance limits for machine types with steady state performance.

Performance limits for machine types with steady state performance

Certain machine types offer steady state performance, a minimum performancelevel that the instance can sustain. The steady state performance is sharedbetween all volumes attached to the instance. For more information, seeSteady state performance.

The following table lists the steady state performance limits for the availablemachine types. If the steady state and maximum performance limits are the same,then the machine type can sustain this performance level in most cases.

Instance machine type	Steady state IOPS	Steady state throughput (MiB/s)	Maximum IOPS	Maximum throughput (MiB/s)
A3 (H200)
a3-ultragpu-8g	500,000	10,000	500,000	10,000
A4
a4-highgpu-8g	500,000	10,000	500,000	10,000
A4X
a4x-highgpu-4g	500,000	10,000	500,000	10,000
C4
c4-*-2	6,200	120	50,000	400
c4-*-4	12,500	240	50,000	400
c4-*-8	25,000	480	50,000	800
c4-*-16	50,000	1,000	100,000	1,600
c4-*-24	75,000	1,200	100,000	1,600
c4-*-32	100,000	1,600	100,000	1,600
c4-*-48	160,000	2,400	160,000	2,400
c4-*-96	350,000	5,000	350,000	5,000
c4-*-144	350,000	5,000	350,000	5,000
c4-*-192	500,000	10,000	500,000	10,000
c4-*-288	500,000	10,000	500,000	10,000
C4D
c4d-*-2	2,800	65	22,500	400
c4d-*-4	6,200	120	50,000	400
c4d-*-8	12,500	240	50,000	800
c4d-*-16	25,000	480	75,000	1,200
c4d-*-32	50,000	1,000	75,000	1,600
c4d-*-48	75,000	1,400	75,000	1,600
c4d-*-64	350,000	5,000	350,000	5,000
c4d-*-96	350,000	5,000	350,000	5,000
c4d-*-192	350,000	5,000	350,000	5,000
c4d-*-384	500,000	10,000	500,000	10,000
H4D
h4d-*-192	15,000	240	15,000	240
M4
m4-*-16	50,000	1,000	100,000	1,600
m4-*-28	50,000	1,000	100,000	1,600
m4-*-32	90,000	1,600	120,000	1,800
m4-*-56	160,000	2,400	160,000	2,400
m4-*-64	160,000	2,900	200,000	3,000
m4-*-112	350,000	5,000	350,000	5,000
m4-*-224	500,000	10,000	500,000	10,000

Performance limits by Hyperdisk type

For the performance limits by machine type for each Hyperdisktype, see the following sections:

• Hyperdisk Balanced
• Hyperdisk Balanced High Availability
• Hyperdisk Extreme
• Hyperdisk ML
• Hyperdisk Throughput

Hyperdisk Balanced performance limits

This section lists the maximum performance that Hyperdisk Balanced volumescan achieve for each supported instance. A Hyperdisk Balanced volume's performancewhen it's attached to an instance can't exceed the limits for the instance'smachine type.The performance limits are also shared across all Hyperdisk Balanced volumesattached to the same instance, regardless of each volume's provisioned performance.

Achieve higher performance with multiple Hyperdisk Balanced volumes

Certain instances can exceed the maximum performance for a single Hyperdisk Balanced volume—160,000 IOPS or 2,400 MiB per second (MiB/s). An instance can onlyachieve these higher limits if you attach multiple Hyperdisk Balanced volumes to the instance.

If an instance's performance limit in the following table exceeds 160,000 IOPS or2,400 MiB/s, then the instance can only achieve that limitif you attach multiple Hyperdisk Balanced volumes.For example, the performance limit for ac4a-*-72 instance using Hyperdisk Balancedis 240,000 IOPS and 5,000 MiB/s. To achieve this maximum performanceyou must attach at least two Hyperdisk Balanced volumes to the instance.

To learn more about Hyperdisk Balanced, seeAbout Hyperdisk Balanced.

Important: To reach the IOPS limits, you must use an I/O size of4 KB. Maximum throughput limits require an I/O size of at least256 KB.
Hyperdisk performance is half-duplex,so the IOPS and throughput limits are shared between read and write operations.This means that if a machine type has a 50,000 IOPS limit, then the sum of the readsand writes every second can't exceed 50,000.

Hyperdisk Balanced High Availability performance limits

This section lists the maximum performance that Hyperdisk Balanced High Availability volumescan achieve for each supported instance. A Hyperdisk Balanced High Availability volume's performancewhen it's attached to an instance can't exceed the limits for the instance'smachine type.The performance limits are also shared across all Hyperdisk Balanced High Availability volumesattached to the same instance, regardless of each volume's provisioned performance.

Achieve higher performance with multiple Hyperdisk Balanced High Availability volumes

Certain instances can exceed the maximum performance for a single Hyperdisk Balanced High Availability volume—100,000 IOPS or 1,200 MiB/s. An instance can achieve thesehigher limits if you attach multiple Hyperdisk Balanced High Availability volumes to the instance.

If an instance's performance limit in the following table exceeds100,000 IOPS or 1,200 MiB/s, then the instance can achieve thatlimit only if you attach multiple Hyperdisk Balanced High Availability volumes.For example, the performance limit for ac4a-*-72 instance using Hyperdisk Balanced High Availabilityis 240,000 IOPS and 5,000 MiB/s. To achieve this maximum performanceyou must attach at least five Hyperdisk Balanced High Availability volumes to the instance.

For information about Hyperdisk Balanced High Availability features, seeAbout Hyperdisk Balanced High Availability.

Important: To reach the IOPS limits, you must use an I/O size of4 KB. Maximum throughput limits require an I/O size of at least256 KB.
Hyperdisk performance is half-duplex,so the IOPS and throughput limits are shared between read and write operations.This means that if a machine type has a 50,000 IOPS limit, then the sum of the readsand writes every second can't exceed 50,000.

Hyperdisk Extreme performance limits

This section lists the maximum performance that Hyperdisk Extreme volumescan achieve for each supported instance. A Hyperdisk Extreme volume's performancewhen it's attached to an instance can't exceed the limits for the instance'smachine type.The performance limits are also shared across all Hyperdisk Extreme volumesattached to the same instance, regardless of each volume's provisioned performance.

Achieve higher performance with multiple Hyperdisk Extreme volumes

Certain instances can exceed the maximum performance for a single Hyperdisk Extreme volume—350,000 IOPS or 5,000  MiB/s. An instance can only achieve thesehigher limits if you attach multiple Hyperdisk Extreme volumes to the instance.

If an instance's performance limit in the following table exceeds 350,000 IOPS or5,000  MiB/s, then the instance can only achieve that limitif you attach multiple Hyperdisk Extreme volumes.For example, the performance limit for ac3-*-176 instance using Hyperdisk Extremeis 500,000 IOPS and 10,000 MiB/s.To achieve this maximum performance you must attach at least two Hyperdisk Extreme volumes to the instance.

For more information about Hyperdisk Extreme, seeAbout Hyperdisk Extreme.

Important: To reach the IOPS limits, you must use an I/O size of4 KB. Maximum throughput limits require an I/O size of at least256 KB. Hyperdisk performance is half-duplex,so the IOPS and throughput limits are shared between read and write operations.This means that if a machine type has a 50,000 IOPS limit, then the sum of the readsand writes every second can't exceed 50,000.

Hyperdisk ML performance limits

This section lists the maximum performance that Hyperdisk ML volumescan achieve for each supported instance. A Hyperdisk ML volume's performancewhen it's attached to an instance can't exceed the limits for the instance'smachine type.The performance limits are also shared across all Hyperdisk ML volumesattached to the same instance, regardless of each volume's provisioned performance.

Scenarios that require multiple instances to reach provisioned performance

The provisioned throughput for a Hyperdisk ML volume is shared between each instance the volume is attached to,up to the maximum limit for the machine type that's listed in the following table.If a Hyperdisk ML volume's provisioned performance is higher than an instance's performance limit,the volume can achieve its provisioned performance only if it is attached to multiple instances.a3-ultragpu-8 instances have a throughput limit of4,000 MiB/s.

For example, suppose you have a Hyperdisk ML volume provisioned with 500,000 MiB/s of throughput.and you want to attach the volume toa3-ultragpu-8 instances. A singlea3-ultragpu-8 instance can't acheieve more than 4,000 MiB/sof throughput. Therefore, to achieve the volume's provisioned throughput, you must attach the volumeto at least 125 (500,000/4,000)a3-ultragpu-8 instances. On theother hand, for thea2-highgpu-1g machine type, you would need 272 instances.

For more information about Hyperdisk ML, seeAbout Hyperdisk ML.

Important: To reach the IOPS limits, you must use an I/O size of4 KB. Maximum throughput limits require an I/O size of at least256 KB. Hyperdisk performance is half-duplex,so the IOPS and throughput limits are shared between read and write operations.This means that if a machine type has a 50,000 IOPS limit, then the sum of the readsand writes every second can't exceed 50,000.

Instance machine type	Maximum IOPS	Maximum throughput (MiB/s)
A2
a2-*-1g	28,800	1,800
a2-*-2g	38,400	2,400
a2-*-4g	38,400	2,400
a2-*-8g	38,400	2,400
a2-megagpu-16g	38,400	2,400
A3 (A3+H100)
a3-*-1g	28,800	1,800
a3-*-2g	38,400	2,400
a3-*-4g	38,400	2,400
a3-*-8g (in read-only mode)1	64,000	4,000
a3-*-8g (in read-write mode)1	38,400	2,400
C3
c3-*-4	6,400	400
c3-*-8	12,800	800
c3-*-22	28,800	1,800
c3-*-44	38,400	2,400
c3-*-88	38,400	2,400
c3-*-176	38,400	2,400
c3-*-192	38,400	2,400
C3D
c3d-*-4	6,400	400
c3d-*-8	12,800	800
c3d-*-16	19,200	1,200
c3d-*-30	19,200	1,200
c3d-*-60	38,400	2,400
c3d-*-90	38,400	2,400
c3d-*-180	38,400	2,400
c3d-*-360	38,400	2,400
G2
g2-standard-4	12,800	800
g2-standard-8	19,200	1,200
g2-standard-12	28,800	1,800
g2-standard-16	38,400	2,400
g2-standard-24	38,400	2,400
g2-standard-32	38,400	2,400
g2-standard-48	38,400	2,400
g2-standard-96	38,400	2,400
TPU v6e
ct6e-standard-1t	19,200	1,200
ct6e-standard-4t	28,800	1,800
ct6e-standard-8t	28,800	1,800

¹Fora3-*-8g instances, performance depends on whether the Hyperdisk ML volume is attached to the instance in read-only or read-write mode.

Hyperdisk Throughput performance limits

This section lists the maximum performance that Hyperdisk Throughput volumescan achieve for each supported instance. A Hyperdisk Throughput volume's performancewhen it's attached to an instance can't exceed the limits for the instance'smachine type.The performance limits are also shared across all Hyperdisk Throughput volumesattached to the same instance, regardless of each volume's provisioned performance.

Achieve higher performance with multiple Hyperdisk Throughput volumes

Certain instances can exceed the maximum performance for a single Hyperdisk Throughputvolume—2,400  MiB/s. An instance can achieve these higher limits if youattach multiple Hyperdisk Throughput volumes to the instance.

If an instance's performance limit in the following table exceeds 2,400 MiB/s,then the instance can achieve that limit only if you attach multiple Hyperdisk Throughput volumes.For example, the performance limit for aa3-*-8g instance using Hyperdisk Throughput volumesis 3,000 MiB/s. Therefore, to achieve 3,000 MiB/s ofthroughput, you must attach at least two Hyperdisk Throughput volumes to the instance.

For more information about Hyperdisk Throughput, seeAbout Hyperdisk Throughput.

Important: To reach the IOPS limits, you must use an I/O size of4 KB. Maximum throughput limits require an I/O size of at least256 KB.
Hyperdisk performance is half-duplex,so the IOPS and throughput limits are shared between read and write operations.This means that if a machine type has a 50,000 IOPS limit, then the sum of the readsand writes every second can't exceed 50,000.

Hyperdisk size and attachment limits

The following sections describe the limits to the size and number ofHyperdisk volumes you can attach to a single instance.The limits discussed don't apply to any Local SSD disks attached to the sameinstance.

Summary of Hyperdisk per-instance limits

Maximum total capacity per instance: The maximum total capacity of all the volumesattached to an instance is between 257 TiB to 512 TiB, depending onvarious factors. For details, seeMaximum total capacity per instance.

Maximum number of volumes attached to an instance: Compute Engine limitsthe number of Hyperdisk volumes that you can attach to a singleinstance. The following limits apply in order. When both limits apply,the first rule in the list is enforced.

1. The number of Hyperdisk volumesthat you can attach to the instance: 8 to 128; depending on theHyperdisk type and theinstance's machine type.
2. The number of Hyperdisk and Persistent Disk volumes that you canattach to the instance: 128. For more information, seeMaximum number of disks, across all types.

The following examples demonstrate how the limits work.

Examples

Suppose you have ac3-*-96 instance. The following limits apply.

• Maximum number of Hyperdisk volumes across all types:128. However, for each Hyperdisktype, the limits are as follows:
  • Hyperdisk Throughput: 64
  • Hyperdisk ML: 64
  • Hyperdisk Extreme: 8
  • Hyperdisk Balanced or Hyperdisk Balanced High Availability: 32
• Maximum number of Persistent Disk and Hyperdisk volumes that youcan attach to the instance: 128
• Maximum combined total capacity of all volumes: 512 TiB

The following examples illustrate these limits.

• Maximum number of a single type of Hyperdisk per instance:If you attach 8 Hyperdisk Extreme volumes to the instance, you can attach up to 123more Hyperdisk volumes to the instance. However, you canattach only 3 more Hyperdisk Extreme volumes to the instance because the maximum numberof Hyperdisk Extreme volumes 8.

• Maximum number of Hyperdisk volumes per instance: 128. Ifyou attach 8 Hyperdisk Extreme volumes to the instance, you can attach up to120 more Hyperdisk volumes to the instance.

• Maximum number of disks or volumes per instance, across all types: 128. Ifyou attach a combined total of 128Hyperdisk volumes to the instance, then you can't attach any moreHyperdisk or Persistent Disk volumes. However, if you attach only64 Hyperdisk volumes to the instance, you canstill attach up to 64 Persistent Disk or Hyperdisk volumes to theinstance.

Maximum total capacity per instance

The maximum total disk capacity (in TiB) across all Hyperdiskand Persistent Disk types that you attach to an instance depends on the number ofvCPUs that the instance has. The capacity limits are as follows:

• For machine types with less than 32 vCPUs:

  • 257 TiB for all Hyperdisk or all Persistent Disk
  • 257 TiB for a mixture of Hyperdisk and Persistent Disk

• For machine types with 32 or more vCPUs:

  • 512 TiB for all Hyperdisk
  • 512 TiB for a mixture of Hyperdisk and Persistent Disk
  • 257 TiB for all Persistent Disk

You can attach a combination of Hyperdisk and Persistent Diskvolumes to a single instance but the total disk capacity for Persistent Disk can'texceed 257 TiB.

Maximum number of disks per instance, across all types

The maximum number of individual Hyperdisk, and, if supported,Persistent Disk volumes that you can attach to an instance is 128. If youattach 28 Hyperdisk volumes to a instance, you can still attachup to 100 more Hyperdisk or Persistent Disk volumes to the sameinstance.

Maximum Hyperdisk volumes per instance

The number of Hyperdisk volumes you can attach to an instancedepends on the machine type, with separate limits for eachHyperdisk type.

For disk attachment limits for TPUs, seeTPU support for Hyperdisk and Persistent Disk.

For all other machine series, the limits are detailed in theSupported disk types section within the documentation for each machineseries. To view these limits, refer to the corresponding links in the followingtable.

General purpose machine types	Compute-optimized machine types	Memory-optimized machine types	Accelerator-optimized machine types	Storage-optimized machine types
C3 C3D C4 C4A C4D N2 N2D N4 N4A N4D T2D	H3 H4D	M1 M2 M3 M4 X4	A2 A3+H100 A3+H200 A4 A4X G2 G4	Z3

What's next

• Learn how tooptimize the performance of your Hyperdisk volumes