About Persistent Disk performance
This page discusses the many factors that determine the performanceof the Persistent Disk volumes and lists the maximum performance limits for Persistent Disk.
For a discussion of Google Cloud Hyperdisk performance, seeAbout performance for Hyperdisk.For about Google Cloud Hyperdisk performance limits,seeHyperdisk performance limits.
Before you begin, consider the following:
Persistent Disk are networked storage and generally have higher latencycompared to physical disks orLocal SSDs.To reach the maximum performance limits of the Persistent Disk, you mustissue enough I/O requests in parallel. To check if you're using a high enoughqueue depth to reach your required performance levels, seeI/O queue depth.
Make sure that your application is issuing enough I/O requests to saturatethe disk. Disk saturation occurs when the CPU time during I/O requestsissued to the device is very high.
For workloads that primarily involve small (from 4 KB to 16 KB)random I/O requests, the limiting performance factor is I/Orequests per second(IOPS).
For workloads that primarily involve sequential or large(256 KB to 1 MB) random I/O requests, the limiting performancefactor isthroughput.
Choose a Persistent Disk type
When you create a Persistent Disk volume, you can select one of the following disktypes:
- Balanced Persistent Disk (
pd-balanced)- An alternative to SSD (Performance) Persistent Disk.
- Balance of performance and cost. For most Compute Engine machinetypes, these disks have the same maximum IOPS asSSD Persistent Disk and lower IOPS per GiB. This disk type offers performancelevels suitable for most general-purpose applications at a price pointbetween that of standard and SSD Persistent Disk.
- Backed by solid-state drives (SSD).
- SSD (Performance) Persistent Disk (
pd-ssd)- Suitable for enterprise applications and high-performance databasesthat require lower latency and more IOPS than standard Persistent Diskprovides.
- Backed by solid-state drives (SSD).
- Standard Persistent Disk (
pd-standard)- Suitable for large data processing workloads that primarily usesequential I/Os.
- Backed by standard hard disk drives (HDD).
- Extreme Persistent Disk (
pd-extreme)- Offers consistently high performance for both random access workloads andbulk throughput.
- Designed for high-end database workloads.
- Lets you provision the target IOPS.
- Backed by solid-state drives (SSD).
- Available with a limited number ofmachine types.
If you create a disk in the Google Cloud console, the default disk type ispd-balanced. If you create a disk using the gcloud CLI or theCompute Engine API, the default disk type ispd-standard.
Each storage option has unique performance limits that depend on themachine type and number of vCPUs in use.
Performance limits for Persistent Disk
Persistent Disk have limits for the maximum IOPS and throughput that they cansustain. There are throughput and IOPS limits per GiB and per instance. BalancedPersistent Disk and SSD (performance) Persistent Disk also offerbaseline performancefor sustained IOPS and throughput. BalancedPersistent Disk, SSD (performance) Persistent Disk, and Extreme Persistent Disk are designedfor sub-millisecond latencies.Factors that affect performanceinclude machine type, disk size, instance vCPU count, and I/O block size.
This page details the performance limits forzonal Persistent Disk andregional Persistent Disk.
Zonal Persistent Disk
This section shows IOPS and throughput limits for zonal Persistent Disk.
IOPS limits for zonal Persistent Disk
The following table shows IOPS limits for zonal Persistent Disk.
| Zonal Standard PD | Zonal Balanced PD | Zonal SSD PD | Zonal Extreme PD | Zonal SSD PD in multi-writer mode | |
|---|---|---|---|---|---|
| Read IOPS per GiB | 0.75 | 6 | 30 | – | 30 |
| Write IOPS per GiB | 1.5 | 6 | 30 | – | 30 |
| Read IOPS per instance* | 7,500 | 80,000 | 100,000 | 120,000 | 100,000 |
| Write IOPS per instance* | 15,000 | 80,000 | 100,000 | 120,000 | 100,000 |
Throughput limits for zonal Persistent Disk
The following table shows throughput limits for zonal Persistent Disk.Persistent Disk can achieve greater performance on instances with more vCPUs.For more information, readNetwork egress caps on write throughput.
| Zonal Standard PD | Zonal Balanced PD | Zonal SSD PD | Zonal Extreme PD | Zonal SSD PD in multi-writer mode | |
|---|---|---|---|---|---|
| Throughput per GiB (MiBps) | 0.12 | 0.28 | 0.48 | — | 0.48 |
| Read throughput per instance (MiBps) | 1,200 | 1,200 | 1,200 | 4,000* | 1,200 |
| Write throughput per instance (MiBps) | 400 | 1,200 | 1,200 | 3,000* | 1,200 |
Regional Persistent Disk
Like zonal Persistent Disk, regional Persistent Disk can achieve greaterperformance when you modifyfactors that can affect performance,like disk size and number of vCPUs.
The following tables show IOPS and throughput limits for regional Persistent Disk.These conditions apply to the stated limits:
- Achieving the stated limits requires a compute instance with at least 64vCPUs and anN2 machinetype or anN1 machinetype running on the Intel Skylake or newer CPU. Instances using other machinetypes, such asN2D,have lower performance limits.
- Instances usingE2machine types have lower performance limits because E2machine types support a maximum of 32 vCPUs.
- Read IOPS per instance and read throughput per instance might be lower whenthe disk is inunreplicated mode.
IOPS limits for regional Persistent Disk
The following table shows IOPS limits for regional Persistent Disk.
| Regional Standard PD | Regional Balanced PD | Regional SSD PD | |
|---|---|---|---|
| Read IOPS per GiB | 0.75 | 6 | 30 |
| Write IOPS per GiB | 1.5 | 6 | 30 |
| Read IOPS per instance | 7,500 | 80,000* | 100,000# |
| Write IOPS per instance | 15,000 | 60,000† | 80,000‡ |
Throughput limits for regional Persistent Disk
The following table shows the throughput limits for regional Persistent Disk.
| Regional Standard PD | Regional Balanced PD | Regional SSD PD | |
|---|---|---|---|
| Read throughput per instance (MiBps) | 1,200 | 1,200 | 1,200 |
| Write throughput per instance (MiBps) | 200 | 600 | 1000‡ |
Sharing disks between instances
Attaching a disk to multiple instances inread-only modemode or inmulti-writer mode does not affect aggregate performance or cost.Each machine gets a share of the per-disk performance limit. Persistent Diskcreated inmulti-writer mode have specific IOPS and throughput limits. Tolearn how to share Persistent Disk between multiple instances, seeSharing Persistent Disk between instances.
Persistent Disk I/O operations share a common path with network traffic within ainstance's hypervisor. Therefore, if the instance has significant network traffic, theactual read bandwidth and IOPS consistency might be less than the listed maximumlimits. Some variability in the performance limits is to be expected, especiallywhen operating near the maximum IOPS limits with an I/O size of 16 KB. Fora summary of bandwidth expectations, seeBandwidth summary table.
Baseline performance
The following Persistent Disk types offer baseline IOPS andthroughput performance in addition to sustained per GiB performance limits:
- Balanced Persistent Disk
- SSD Persistent Disk
Baseline performance is the same for all disk sizes and doesn't scale based onthe number of disks of the same type that are attached to an instance. Forexample, if you have two zonal balanced Persistent Disk attached to an instance,they share a baseline performance of 3,000 IOPS.
To calculate the maximum expected performance of a Persistent Disk type, add thedisk type's baseline performance to the per GiB performance limit for the disktype multiplied by the combined size (in GiB) of all disks of thesame type that are attached to the instance:
Maximum expected performance = Baseline performance + (Per GiB performancelimit * Combined disk size in GiB).
For example, the maximum IOPS of two 1000 GiB zonal balanced Persistent Diskattached to the same instance is 15,000, which is calculated as follows:
3,000 baseline performance + (6 IOPS performance limit per GiB *2000 GiB combined disk size) = 15,000 IOPS
The following table shows the baseline performance for balanced and SSDPersistent Disk.
Zonal Persistent Disk
The following table shows the baseline sustained IOPS and throughput for zonalPersistent Disk:
| Zonal balanced PD | Zonal SSD PD | |
|---|---|---|
| Baseline IOPS per instance | 3,000 | 6,000 |
| Baseline Throughput (MiBps) per instance | 140 | 240 |
Regional Persistent Disk
Regional Persistent Disk are supported on only E2, N1, N2, and N2D instances. Thefollowing table shows the baseline sustained IOPS and throughputfor regional Persistent Disk:
| Regional balanced PD | Regional SSD PD | |
|---|---|---|
| Baseline IOPS per instance | 3,000 | 6,000 |
| Baseline Throughput (MiBps) per instance | 140 | 240 |
Configure your Persistent Disk and instances
Persistent Disk performance scales with the size of the disk and with thenumber of vCPUs on your instance.
Performance scales until it reaches either the limits of the disk orthe limits of the instance to which the disk is attached. Themachine type and the number of vCPUs on the instancedetermine the per-instance limits.
The following tables show performance limits for zonal Persistent Disk.
Performance by machine type and vCPU count for zonal Persistent Disk
The following tables show how zonal Persistent Disk performance varies accordingto the machine type and number of vCPUs on the instance to which the disk isattached.
A2 Ultra instances
pd-balanced
| Machine type | Maximum write IOPS | Maximum read IOPS | Maximum write throughput (MiBps) | Maximum read throughput (MiBps) |
|---|---|---|---|---|
| a2-ultragpu-1g | 15,000 | 15,000 | 800 | 800 |
| a2-ultragpu-2g | 20,000 | 20,000 | 1,200 | 1,200 |
| a2-ultragpu-4g | 50,000 | 50,000 | 1,200 | 1,200 |
| a2-ultragpu-8g | 80,000 | 80,000 | 1,200 | 1,200 |
pd-ssd
| Machine type | Maximum write IOPS | Maximum read IOPS | Maximum write throughput (MiBps) | Maximum read throughput (MiBps) |
|---|---|---|---|---|
| a2-ultragpu-1g | 15,000 | 15,000 | 800 | 800 |
| a2-ultragpu-2g | 25,000 | 25,000 | 1,200 | 1,200 |
| a2-ultragpu-4g | 60,000 | 60,000 | 1,200 | 1,200 |
| a2-ultragpu-8g | 100,000 | 100,000 | 1,200 | 1,200 |
pd-standard
| Machine type | Maximum write IOPS | Maximum read IOPS | Maximum write throughput (MiBps) | Maximum read throughput (MiBps) |
|---|---|---|---|---|
| a2-ultragpu-1g | 15,000 | 5,000 | 400 | 800 |
| a2-ultragpu-2g | 15,000 | 7,500 | 400 | 1,200 |
| a2-ultragpu-4g | 15,000 | 7,500 | 400 | 1,200 |
| a2-ultragpu-8g | 15,000 | 7,500 | 400 | 1,200 |
A2 Standard instances
pd-balanced
| Machine type | Maximum write IOPS | Maximum read IOPS | Maximum write throughput (MiBps) | Maximum read throughput (MiBps) |
|---|---|---|---|---|
| a2-highgpu-1g | 15,000 | 15,000 | 800 | 800 |
| a2-highgpu-2g | 20,000 | 20,000 | 1,200 | 1,200 |
| a2-highgpu-4g | 50,000 | 50,000 | 1,200 | 1,200 |
| a2-highgpu-8g | 80,000 | 80,000 | 1,200 | 1,200 |
| a2-megagpu-16g | 80,000 | 80,000 | 1,200 | 1,200 |
pd-ssd
| Machine type | Maximum write IOPS | Maximum read IOPS | Maximum write throughput (MiBps) | Maximum read throughput (MiBps) |
|---|---|---|---|---|
| a2-highgpu-1g | 15,000 | 15,000 | 800 | 800 |
| a2-highgpu-2g | 25,000 | 25,000 | 1,200 | 1,200 |
| a2-highgpu-4g | 60,000 | 60,000 | 1,200 | 1,200 |
| a2-highgpu-8g | 100,000 | 100,000 | 1,200 | 1,200 |
| a2-megagpu-16g | 100,000 | 100,000 | 1,200 | 1,200 |
pd-standard
| Machine type | Maximum write IOPS | Maximum read IOPS | Maximum write throughput (MiBps) | Maximum read throughput (MiBps) |
|---|---|---|---|---|
| a2-highgpu-1g | 15,000 | 5,000 | 400 | 800 |
| a2-highgpu-2g | 15,000 | 7,500 | 400 | 1,200 |
| a2-highgpu-4g | 15,000 | 7,500 | 400 | 1,200 |
| a2-highgpu-8g | 15,000 | 7,500 | 400 | 1,200 |
| a2-megagpu-16g | 15,000 | 7,500 | 400 | 1,200 |
A3 Mega instances
pd-balanced
| Machine type | Maximum write IOPS | Maximum read IOPS | Maximum write throughput (MB/s) | Maximum read throughput (MB/s) |
|---|---|---|---|---|
| a3-megagpu-8g | 80,000 | 80,000 | 1,200 | 1,200 |
pd-ssd
| Machine type | Maximum write IOPS | Maximum read IOPS | Maximum write throughput (MB/s) | Maximum read throughput (MB/s) |
|---|---|---|---|---|
| a3-megagpu-8g | 80,000 | 80,000 | 1,200 | 1,200 |
A3 High instances
Note: These machine types use the NVMe disk interface for Persistent Disk.pd-balanced
| Machine type | Maximum write IOPS | Maximum read IOPS | Maximum write throughput (MB/s) | Maximum read throughput (MB/s) |
|---|---|---|---|---|
| a3-highgpu-1g | 15,000 | 15,000 | 1,200 | 1,200 |
| a3-highgpu-2g | 30,000 | 30,000 | 1,200 | 1,200 |
| a3-highgpu-4g | 60,000 | 60,000 | 1,200 | 1,200 |
| a3-highgpu-8g | 80,000 | 80,000 | 1,200 | 1,200 |
pd-ssd
| Machine type | Maximum write IOPS | Maximum read IOPS | Maximum write throughput (MB/s) | Maximum read throughput (MB/s) |
|---|---|---|---|---|
| a3-highgpu-1g | 15,000 | 15,000 | 1,200 | 1,200 |
| a3-highgpu-2g | 30,000 | 30,000 | 1,200 | 1,200 |
| a3-highgpu-4g | 60,000 | 60,000 | 1,200 | 1,200 |
| a3-highgpu-8g | 80,000 | 80,000 | 1,200 | 1,200 |
A3 Edge instances
Note: These machine types use the NVMe disk interface for Persistent Disk.pd-balanced
| Machine type | Maximum write IOPS | Maximum read IOPS | Maximum write throughput (MB/s) | Maximum read throughput (MB/s) |
|---|---|---|---|---|
| a3-edgegpu-8g | 80,000 | 80,000 | 1,200 | 1,200 |
pd-ssd
| Machine type | Maximum write IOPS | Maximum read IOPS | Maximum write throughput (MB/s) | Maximum read throughput (MB/s) |
|---|---|---|---|---|
| a3-edgegpu-8g | 80,000 | 80,000 | 1,200 | 1,200 |
C2 instances
pd-balanced
| Number of vCPUs | Maximum write IOPS | Maximum read IOPS | Maximum write throughput (MiBps) | Maximum read throughput (MiBps) |
|---|---|---|---|---|
| 4 | 4,000 | 4,000 | 240 | 240 |
| 8 | 4,000 | 4,000 | 240 | 240 |
| 16 | 4,000 | 8,000 | 480 | 600 |
| 30 | 8,000 | 15,000 | 480 | 600 |
| 60 | 15,000 | 15,000 | 800 | 1,200 |
pd-ssd
| Number of vCPUs | Maximum write IOPS | Maximum read IOPS | Maximum write throughput (MiBps) | Maximum read throughput (MiBps) |
|---|---|---|---|---|
| 4 | 4,000 | 4,000 | 240 | 240 |
| 8 | 4,000 | 4,000 | 240 | 240 |
| 16 | 4,000 | 8,000 | 480 | 600 |
| 30 | 8,000 | 15,000 | 480 | 600 |
| 60 | 15,000 | 30,000 | 800 | 1,200 |
pd-standard
| Number of vCPUs | Maximum write IOPS | Maximum read IOPS | Maximum write throughput (MiBps) | Maximum read throughput (MiBps) |
|---|---|---|---|---|
| 4 | 4,000 | 3,000 | 240 | 240 |
| 8 | 4,000 | 3,000 | 240 | 240 |
| 16 | 4,000 | 3,000 | 240 | 240 |
| 30 | 8,000 | 3,000 | 240 | 240 |
| 60 | 15,000 | 3,000 | 240 | 240 |
C2D Instances
pd-balanced
| Number of vCPUs | Maximum write IOPS | Maximum read IOPS | Maximum write throughput (MiBps) | Maximum read throughput (MiBps) |
|---|---|---|---|---|
| 2 | 4,590 | 4,080 | 245 | 245 |
| 4 | 4,590 | 4,080 | 245 | 245 |
| 8 | 4,590 | 4,080 | 245 | 245 |
| 16 | 4,590 | 8,160 | 245 | 326 |
| 32 | 8,160 | 15,300 | 245 | 612 |
| 56 | 8,160 | 15,300 | 245 | 612 |
| 112 | 15,300 | 30,600 | 408 | 1,224 |
pd-ssd
| Number of vCPUs | Maximum write IOPS | Maximum read IOPS | Maximum write throughput (MiBps) | Maximum read throughput (MiBps) |
|---|---|---|---|---|
| 2 | 4,590 | 4,080 | 245 | 245 |
| 4 | 4,590 | 4,080 | 245 | 245 |
| 8 | 4,590 | 4,080 | 245 | 245 |
| 16 | 4,590 | 8,160 | 245 | 326 |
| 32 | 8,160 | 15,300 | 245 | 612 |
| 56 | 8,160 | 15,300 | 245 | 612 |
| 112 | 15,300 | 30,600 | 408 | 1,224 |
pd-standard
| Number of vCPUs | Maximum write IOPS | Maximum read IOPS | Maximum write throughput (MiBps) | Maximum read throughput (MiBps) |
|---|---|---|---|---|
| 2 | 4,590 | 3,060 | 245 | 245 |
| 4 | 4,590 | 3,060 | 245 | 245 |
| 8 | 4,590 | 3,060 | 245 | 245 |
| 16 | 4,590 | 3,060 | 245 | 245 |
| 32 | 8,160 | 3,060 | 245 | 245 |
| 56 | 8,160 | 3,060 | 245 | 245 |
| 112 | 15,300 | 3,060 | 245 | 245 |
C3D Instances
Note: These machine types use the NVMe disk interface for Persistent Disk.pd-balanced
| Number of vCPUs | Maximum write IOPS | Maximum read IOPS | Maximum write throughput (MiBps) | Maximum read throughput (MiBps) |
|---|---|---|---|---|
| 4 | 15,000 | 15,000 | 240 | 240 |
| 8 | 25,000 | 25,000 | 800 | 800 |
| 16 | 25,000 | 25,000 | 1,200 | 1,200 |
| 30 | 50,000 | 50,000 | 1,200 | 1,200 |
| 60 | 80,000 | 80,000 | 1,200 | 1,200 |
| 90 | 80,000 | 80,000 | 1,200 | 1,200 |
| 180 | 80,000 | 80,000 | 1,200 | 1,200 |
| 360 | 80,000 | 80,000 | 1,200 | 1,200 |
pd-ssd
| Number of vCPUs | Maximum write IOPS | Maximum read IOPS | Maximum write throughput (MiBps) | Maximum read throughput (MiBps) |
|---|---|---|---|---|
| 4 | 15,000 | 15,000 | 240 | 240 |
| 8 | 15,000 | 15,000 | 800 | 800 |
| 16 | 25,000 | 25,000 | 1,200 | 1,200 |
| 30 | 60,000 | 60,000 | 1,200 | 1,200 |
| 60 | 80,000 | 80,000 | 1,200 | 1,200 |
| 90 | 80,000 | 80,000 | 1,200 | 1,200 |
| 180 | 80,000 | 80,000 | 1,200 | 1,200 |
| 360 | 80,000 | 80,000 | 1,200 | 1,200 |
C3 Instances
Note: These machine types use the NVMe disk interface for Persistent Disk.pd-balanced
| Number of vCPUs | Maximum write IOPS | Maximum read IOPS | Maximum write throughput (MiBps) | Maximum read throughput (MiBps) |
|---|---|---|---|---|
| 4 | 15,000 | 15,000 | 240 | 240 |
| 8 | 15,000 | 15,000 | 240 | 240 |
| 22 | 20,000 | 20,000 | 800 | 800 |
| 44 | 50,000 | 50,000 | 1,200 | 1,200 |
| 88 | 80,000 | 80,000 | 1,200 | 1,200 |
| 176 | 80,000 | 80,000 | 1,200 | 1,200 |
pd-ssd
| Number of vCPUs | Maximum write IOPS | Maximum read IOPS | Maximum write throughput (MiBps) | Maximum read throughput (MiBps) |
|---|---|---|---|---|
| 4 | 15,000 | 15,000 | 240 | 240 |
| 8 | 15,000 | 15,000 | 240 | 240 |
| 22 | 25,000 | 25,000 | 800 | 800 |
| 44 | 60,000 | 60,000 | 1,200 | 1,200 |
| 88 | 80,000 | 80,000 | 1,200 | 1,200 |
| 176 | 80,000 | 80,000 | 1,200 | 1,200 |
E2 Instances
pd-balanced
| Number of vCPUs | Maximum write IOPS | Maximum read IOPS | Maximum write throughput (MiBps) | Maximum read throughput (MiBps) |
|---|---|---|---|---|
| e2-medium* | 10,000 | 12,000 | 200 | 200 |
| 2-7 | 15,000 | 15,000 | 240 | 240 |
| 8-15 | 15,000 | 15,000 | 800 | 800 |
| 16-31 | 20,000 | 20,000 | 1,000 | 1,200 |
| 32 or more | 50,000 | 50,000 | 1,000 | 1,200 |
pd-ssd
| Number of vCPUs | Maximum write IOPS | Maximum read IOPS | Maximum write throughput (MiBps) | Maximum read throughput (MiBps) |
|---|---|---|---|---|
| e2-medium* | 10,000 | 12,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,000 | 1,200 |
| 32 or more | 60,000 | 60,000 | 1,000 | 1,200 |
pd-standard
| Number of vCPUs | Maximum write IOPS | Maximum read IOPS | Maximum write throughput (MiBps) | Maximum read throughput (MiBps) |
|---|---|---|---|---|
| e2-medium* | 10,000 | 1,000 | 200 | 200 |
| 2-7 | 15,000 | 3,000 | 240 | 240 |
| 8-15 | 15,000 | 5,000 | 400 | 800 |
| 16 or more | 15,000 | 7,500 | 400 | 1,200 |
G2 Instances
Note: These machine types use the NVMe disk interface for Persistent Disk.pd-balanced
| Machine type | Maximum write IOPS | Maximum read IOPS | Maximum write throughput (MiBps) | Maximum read throughput (MiBps) |
|---|---|---|---|---|
| g2-standard-4 | 15,000 | 15,000 | 240 | 240 |
| g2-standard-8 | 15,000 | 15,000 | 800 | 800 |
| g2-standard-12 | 15,000 | 15,000 | 800 | 800 |
| g2-standard-16 | 20,000 | 20,000 | 1,200 | 1,200 |
| g2-standard-24 | 20,000 | 20,000 | 1,200 | 1,200 |
| g2-standard-32 | 50,000 | 50,000 | 1,200 | 1,200 |
| g2-standard-48 | 50,000 | 50,000 | 1,200 | 1,200 |
| g2-standard-96 | 80,000 | 80,000 | 1,200 | 1,200 |
pd-ssd
| Machine type | Maximum write IOPS | Maximum read IOPS | Maximum write throughput (MiBps) | Maximum read throughput (MiBps) |
|---|---|---|---|---|
| g2-standard-4 | 15,000 | 15,000 | 240 | 240 |
| g2-standard-8 | 15,000 | 15,000 | 800 | 800 |
| g2-standard-12 | 15,000 | 15,000 | 800 | 800 |
| g2-standard-16 | 25,000 | 25,000 | 1,200 | 1,200 |
| g2-standard-24 | 25,000 | 25,000 | 1,200 | 1,200 |
| g2-standard-32 | 60,000 | 60,000 | 1,200 | 1,200 |
| g2-standard-48 | 60,000 | 60,000 | 1,200 | 1,200 |
| g2-standard-96 | 100,000 | 100,000 | 1,200 | 1,200 |
H3 Instances
Note: These machine types use the NVMe disk interface for Persistent Disk.pd-balanced
| Number of vCPUs | Maximum write IOPS | Maximum read IOPS | Maximum write throughput (MiBps) | Maximum read throughput (MiBps) |
|---|---|---|---|---|
| 88 | 15,000 | 15,000 | 240 | 240 |
N1 Instances
pd-balanced
| Number of vCPUs | Maximum write IOPS | Maximum read IOPS | Maximum write throughput (MiBps) | Maximum read throughput (MiBps) |
|---|---|---|---|---|
| 1 | 15,000 | 15,000 | 204 | 240 |
| 2-7 | 15,000 | 15,000 | 240 | 240 |
| 8-15 | 15,000 | 15,000 | 800 | 800 |
| 16-31 | 20,000 | 20,000 | 1,200 | 1,200 |
| 32-63 | 50,000 | 50,000 | 1,200 | 1,200 |
| 64 or more | 80,000 | 80,000 | 1,200 | 1,200 |
pd-ssd
| Number of vCPUs | Maximum write IOPS | Maximum read IOPS | Maximum write throughput (MiBps) | Maximum read throughput (MiBps) | |
|---|---|---|---|---|---|
| 1 | 15,000 | 15,000 | 204 | 240 | |
| 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 or more | 100,000 | 100,000 | 1,200 | 1,200 |
pd-standard
| Number of vCPUs | Maximum write IOPS | Maximum read IOPS | Maximum write throughput (MiBps) | Maximum read throughput (MiBps) |
|---|---|---|---|---|
| 1 | 15,000 | Up to 3,000 | 204 | 240 |
| 2-7 | 15,000 | 3,000 | 240 | 240 |
| 8-15 | 15,000 | 5,000 | 400 | 800 |
| 16 or more | 15,000 | 7,500 | 400 | 1,200 |
N2 Instances
pd-balanced
| Number of vCPUs | Maximum write IOPS | Maximum read IOPS | Maximum write throughput (MiBps) | Maximum read throughput (MiBps) |
|---|---|---|---|---|
| 2-7 | 15,000 | 15,000 | 240 | 240 |
| 8-15 | 15,000 | 15,000 | 800 | 800 |
| 16-31 | 20,000 | 20,000 | 1,200 | 1,200 |
| 32-63 | 50,000 | 50,000 | 1,200 | 1,200 |
| 64 or more | 80,000 | 80,000 | 1,200 | 1,200 |
pd-ssd
| Number of vCPUs | Maximum write IOPS | Maximum read IOPS | Maximum write throughput (MiBps) | Maximum read throughput (MiBps) |
|---|---|---|---|---|
| 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 or more | 100,000 | 100,000 | 1,200 | 1,200 |
pd-standard
| Number of vCPUs | Maximum write IOPS | Maximum read IOPS | Maximum write throughput (MiBps) | Maximum read throughput (MiBps) |
|---|---|---|---|---|
| 2-7 | 15,000 | 3,000 | 240 | 240 |
| 8-15 | 15,000 | 5,000 | 400 | 800 |
| 16 or more | 15,000 | 7,500 | 400 | 1,200 |
pd-extreme
| Machine type | Maximum write IOPS | Maximum read IOPS | Maximum write throughput (MiBps) | Maximum read throughput (MiBps) |
|---|---|---|---|---|
| n2-standard-64 | 120,000 | 120,000 | 3,000 | 4,000 |
| n2-standard-80 | 120,000 | 120,000 | 3,000 | 4,000 |
| n2-standard-96 | 120,000 | 120,000 | 3,000 | 4,000 |
| n2-standard-128 | 120,000 | 120,000 | 3,000 | 4,000 |
| n2-highmem-64 | 120,000 | 120,000 | 3,000 | 4,000 |
| n2-highmem-80 | 120,000 | 120,000 | 3,000 | 4,000 |
| n2-highmem-96 | 120,000 | 120,000 | 3,000 | 4,000 |
| n2-highmem-128 | 120,000 | 120,000 | 3,000 | 4,000 |
| n2-highcpu-64 | 120,000 | 120,000 | 3,000 | 4,000 |
| n2-highcpu-80 | 120,000 | 120,000 | 3,000 | 4,000 |
| n2-highcpu-96 | 120,000 | 120,000 | 3,000 | 4,000 |
N2 Instances with 96 or more vCPUs require the Intel Ice Lake CPU platform.
N2D Instances
pd-balanced
| Number of vCPUs | Maximum write IOPS | Maximum read IOPS | Maximum write throughput (MiBps) | Maximum read throughput (MiBps) |
|---|---|---|---|---|
| 2-7 | 15,000 | 15,000 | 240 | 240 |
| 8-15 | 15,000 | 15,000 | 800 | 800 |
| 16-31 | 20,000 | 20,000 | 1,200 | 1,200 |
| 32-63 | 50,000 | 50,000 | 1,200 | 1,200 |
| 64 or more | Up to 80,000 | Up to 80,000 | 1,200 | 1,200 |
pd-ssd
| Number of vCPUs | Maximum write IOPS | Maximum read IOPS | Maximum write throughput (MiBps) | Maximum read throughput (MiBps) |
|---|---|---|---|---|
| 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 or more | Up to 100,000 | Up to 100,000 | 1,200 | 1,200 |
pd-standard
| Number of vCPUs | Maximum write IOPS | Maximum read IOPS | Maximum write throughput (MiBps) | Maximum read throughput (MiBps) |
|---|---|---|---|---|
| 2-7 | 15,000 | 3,000 | 240 | 240 |
| 8-15 | 15,000 | 5,000 | 400 | 800 |
| 16 or more | 15,000 | 7,500 | 400 | 1,200 |
M1 Instances
pd-balanced
| Machine type | Maximum write IOPS | Maximum read IOPS | Maximum write throughput (MiBps) | Maximum read throughput (MiBps) |
|---|---|---|---|---|
| m1-megamem-96 | 80,000 | 80,000 | 1,200 | 1,200 |
| m1-ultramem-40 | 60,000 | 60,000 | 1,200 | 1,200 |
| m1-ultramem-80 | 70,000 | 70,000 | 1,200 | 1,200 |
| m1-ultramem-160 | 70,000 | 70,000 | 1,200 | 1,200 |
pd-ssd
| Machine type | Maximum write IOPS | Maximum read IOPS | Maximum write throughput (MiBps) | Maximum read throughput (MiBps) |
|---|---|---|---|---|
| m1-megamem-96 | 100,000 | 100,000 | 1,200 | 1,200 |
| m1-ultramem-40 | 60,000 | 60,000 | 1,200 | 1,200 |
| m1-ultramem-80 | 70,000 | 70,000 | 1,200 | 1,200 |
| m1-ultramem-160 | 70,000 | 70,000 | 1,200 | 1,200 |
pd-standard
| Machine type | Maximum write IOPS | Maximum read IOPS | Maximum write throughput (MiBps) | Maximum read throughput (MiBps) |
|---|---|---|---|---|
| m1-megamem-96 | 15,000 | 7,500 | 400 | 1,200 |
| m1-ultramem-40 | 15,000 | 7,500 | 400 | 1,200 |
| m1-ultramem-80 | 15,000 | 7,500 | 400 | 1,200 |
| m1-ultramem-160 | 15,000 | 7,500 | 400 | 1,200 |
pd-extreme
| Machine type | Maximum write IOPS | Maximum read IOPS | Maximum write throughput (MiBps) | Maximum read throughput (MiBps) |
|---|---|---|---|---|
| m1-megamem-96 | 90,000 | 90,000 | 2,200 | 2,200 |
M2 Instances
pd-balanced
| Machine type | Maximum write IOPS | Maximum read IOPS | Maximum write throughput (MiBps) | Maximum read throughput (MiBps) |
|---|---|---|---|---|
| m2-megamem-416 | 40,000 | 40,000 | 1,200 | 1,200 |
| m2-ultramem-208 | 40,000 | 40,000 | 1,200 | 1,200 |
| m2-ultramem-416 | 40,000 | 40,000 | 1,200 | 1,200 |
| m2-hypermem-416 | 40,000 | 40,000 | 1,200 | 1,200 |
pd-ssd
| Machine type | Maximum write IOPS | Maximum read IOPS | Maximum write throughput (MiBps) | Maximum read throughput (MiBps) |
|---|---|---|---|---|
| m2-megamem-416 | 40,000 | 40,000 | 1,200 | 1,200 |
| m2-ultramem-208 | 40,000 | 40,000 | 1,200 | 1,200 |
| m2-ultramem-416 | 40,000 | 40,000 | 1,200 | 1,200 |
| m2-hypermem-416 | 40,000 | 40,000 | 1,200 | 1,200 |
pd-standard
| Machine type | Maximum write IOPS | Maximum read IOPS | Maximum write throughput (MiBps) | Maximum read throughput (MiBps) |
|---|---|---|---|---|
| m2-megamem-416 | 15,000 | 7,500 | 400 | 1,200 |
| m2-ultramem-208 | 15,000 | 7,500 | 400 | 1,200 |
| m2-ultramem-416 | 15,000 | 7,500 | 400 | 1,200 |
| m2-hypermem-416 | 15,000 | 7,500 | 400 | 1,200 |
pd-extreme
| Machine type | Maximum write IOPS | Maximum read IOPS | Maximum write throughput (MiBps) | Maximum read throughput (MiBps) |
|---|---|---|---|---|
| m2-megamem-416 | 40,000 | 40,000 | 1,200 | 2,200 |
| m2-ultramem-208 | 40,000 | 40,000 | 1,200 | 2,200 |
| m2-ultramem-416 | 40,000 | 40,000 | 1,200 | 2,200 |
| m2-hypermem-416 | 40,000 | 40,000 | 1,200 | 2,200 |
M3 Instances
Note: These machine types use the NVMe disk interface for Persistent Disk.pd-balanced
| Machine type | Maximum write IOPS | Maximum read IOPS | Maximum write throughput (MiBps) | Maximum read throughput (MiBps) |
|---|---|---|---|---|
| m3-megamem-64 | 40,000 | 40,000 | 1,200 | 1,200 |
| m3-megamem-128 | 80,000 | 80,000 | 1,200 | 1,200 |
| m3-ultramem-32 | 40,000 | 40,000 | 1,200 | 1,200 |
| m3-ultramem-64 | 40,000 | 40,000 | 1,200 | 1,200 |
| m3-ultramem-128 | 80,000 | 80,000 | 1,200 | 1,200 |
pd-ssd
| Machine type | Maximum write IOPS | Maximum read IOPS | Maximum write throughput (MiBps) | Maximum read throughput (MiBps) |
|---|---|---|---|---|
| m3-megamem-64 | 40,000 | 40,000 | 1,200 | 1,200 |
| m3-megamem-128 | 80,000 | 80,000 | 1,200 | 1,200 |
| m3-ultramem-32 | 40,000 | 40,000 | 1,200 | 1,200 |
| m3-ultramem-64 | 40,000 | 40,000 | 1,200 | 1,200 |
| m3-ultramem-128 | 80,000 | 80,000 | 1,200 | 1,200 |
pd-extreme
| Machine type | Maximum write IOPS | Maximum read IOPS | Maximum write throughput (MiBps) | Maximum read throughput (MiBps) |
|---|---|---|---|---|
| m3-megamem-64 | 40,000 | 40,000 | 1,200 | 2,200 |
| m3-megamem-128 | 80,000 | 80,000 | 1,700 | 2,200 |
| m3-ultramem-32 | 40,000 | 40,000 | 1,200 | 2,200 |
| m3-ultramem-64 | 40,000 | 40,000 | 1,200 | 2,200 |
| m3-ultramem-128 | 80,000 | 80,000 | 1,700 | 2,200 |
T2D Instances
pd-balanced
| Number of vCPUs | Maximum write IOPS | Maximum read IOPS | Maximum write throughput (MiBps) | Maximum read throughput (MiBps) |
|---|---|---|---|---|
| 1 | 15,000 | 15,000 | 204 | 240 |
| 2-7 | 15,000 | 15,000 | 240 | 240 |
| 8-15 | 15,000 | 15,000 | 800 | 800 |
| 16-31 | 20,000 | 20,000 | 1,200 | 1,200 |
| 32-60 | 50,000 | 50,000 | 1,200 | 1,200 |
pd-ssd
| Number of vCPUs | Maximum write IOPS | Maximum read IOPS | Maximum write throughput (MiBps) | Maximum read throughput (MiBps) |
|---|---|---|---|---|
| 1 | 15,000 | 15,000 | 204 | 240 |
| 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-60 | 60,000 | 60,000 | 1,200 | 1,200 |
pd-standard
| Number of vCPUs | Maximum write IOPS | Maximum read IOPS | Maximum write throughput (MiBps) | Maximum read throughput (MiBps) |
|---|---|---|---|---|
| 1 | 15,000 | 3,000 | 204 | 240 |
| 2-7 | 15,000 | 3,000 | 240 | 240 |
| 8-15 | 15,000 | 5,000 | 400 | 800 |
| 16 or more | 15,000 | 7,500 | 400 | 1,200 |
T2A Instances
Note: These machine types use the NVMe disk interface for Persistent Disk.pd-balanced
| Number of vCPUs | Maximum write IOPS | Maximum read IOPS | Maximum write throughput (MiBps) | Maximum read throughput (MiBps) |
|---|---|---|---|---|
| 1 | 20,000 | 20,000 | 204 | 240 |
| 2-7 | 20,000 | 20,000 | 240 | 240 |
| 8-15 | 25,000 | 25,000 | 800 | 800 |
| 16-31 | 25,000 | 25,000 | 1,200 | 1,200 |
| 32-47 | 60,000 | 60,000 | 1,200 | 1,200 |
| 48 | 80,000 | 80,000 | 1,800 | 1,800 |
pd-ssd
| Number of vCPUs | Maximum write IOPS | Maximum read IOPS | Maximum write throughput (MiBps) | Maximum read throughput (MiBps) |
|---|---|---|---|---|
| 1 | 20,000 | 20,000 | 204 | 240 |
| 2-7 | 20,000 | 20,000 | 240 | 240 |
| 8-15 | 25,000 | 25,000 | 800 | 800 |
| 16-31 | 25,000 | 25,000 | 1,200 | 1,200 |
| 32-47 | 60,000 | 60,000 | 1,200 | 1,200 |
| 48 | 80,000 | 80,000 | 1,800 | 1,800 |
pd-standard
| Number of vCPUs | Maximum write IOPS | Maximum read IOPS | Maximum write throughput (MiBps) | Maximum read throughput (MiBps) |
|---|---|---|---|---|
| 1 | 15,000 | 1,000 | 204 | 240 |
| 2-3 | 15,000 | 2,400 | 240 | 240 |
| 4-7 | 15,000 | 3,000 | 240 | 240 |
| 8-15 | 15,000 | 5,000 | 400 | 800 |
| 16 or more | 15,000 | 7,500 | 400 | 1,200 |
Z3 Instances
Note: These machine types use the NVMe disk interface for Persistent Disk.pd-balanced
| Number of vCPUs | Maximum write IOPS | Maximum read IOPS | Maximum write throughput (MiBps) | Maximum read throughput (MiBps) |
|---|---|---|---|---|
| 14 to 22 | 20,000 | 20,000 | 800 | 800 |
| 44 | 50,000 | 50,000 | 800 | 800 |
| 88 | 80,000 | 80,000 | 1,200 | 1,200 |
| 176 | 80,000 | 80,000 | 1,200 | 1,200 |
pd-ssd
| Number of vCPUs | Maximum write IOPS | Maximum read IOPS | Maximum write throughput (MiBps) | Maximum read throughput (MiBps) |
|---|---|---|---|---|
| 14 to 22 | 25,000 | 25,000 | 800 | 800 |
| 44 | 60,000 | 60,000 | 800 | 800 |
| 88 | 100,000 | 100,000 | 1,200 | 1,200 |
| 176 | 100,000 | 100,000 | 1,200 | 1,200 |
Example
Consider a 1,000 GiB zonal SSD Persistent Disk attached to an N2 instance with 4vCPUs. The read limit based solely on the size of the disk is36,000 IOPS (6,000 baseline IOPs + (30 IOPS per GiB * 1,000 GiB)). However, theinstance has only 4 vCPUs so the read limit is restricted to 15,000 IOPS.
Review performance
You can review Persistent Disk performance metrics inCloud Monitoring,Google Cloud's integrated monitoring solution.
To learn more, seeReviewing Persistent Disk performance metrics.
Optimize disk performance
To increase disk performance, start with the following steps:
Resize your Persistent Diskto increase the per-disk IOPS and throughput limits. Persistent Disk don'thave any reserved, unusable capacity, so you can use the full disk withoutperformance degradation. However, certain file systems and applicationsmight perform worse as the disk becomes full, so you might need to considerincreasing the size of your disk to avoid such situations.
Change the machine typeand number of vCPUs on the instance to increase the per-instance IOPS andthroughput limits.
After choosing the right disk size and machine type for your instance to resolveany performance bottlenecks, your application and OS might need additionaltuning. For more information, seeOptimizing Persistent Disk performanceandOptimizing Local SSD performance.
What's next
- Benchmark yourLocal SSDsandPersistent Disk thatare attached to Linux instances.
- Optimize yourPersistent DiskandLocal SSDperformance.
- Learn aboutPersistent Disk andLocal SSD pricing.
- Learn how to review your project log entriesusing the Logs Explorer.
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-09 UTC.