This document describes the features of Hyperdisk Throughput. Hyperdisk Throughput is best forcost-sensitive and analytics workloads that require up to2,400 MiB/s of throughput per volume. It's also a goodfit for workloads that use sequential I/O and large block sizes.

For more information about Hyperdisk and the otherHyperdisk types, seeAbout Hyperdisk.

You can specify up to 2,400 MiB/sof throughput for a single Hyperdisk Throughput volume. You can't provision an IOPSlevel, but each MiB/s of provisioned throughput comes with 4IOPS, up to 9,600 IOPS.
Hyperdisk Throughput has a latency profile similar to hard-disk based storage, with averageread latency of 10-30 milliseconds.

To create a new Hyperdisk Throughput volume, seeCreate a Hyperdisk volume.

Use cases

Hyperdisk Throughput is a good fit for the following use cases:

• Analytic workloads like Kafka and Hadoop
• Cold storage
• Data drives for cost-sensitive workloads

Machine series support

You can use Hyperdisk Throughput with the following machine series. You can't use Hyperdisk Throughput with bare metal instances.

• C4
• C4A
• C3
• C3D
• N4
• N4A (Preview)
• N4D
• N2
• N2D
• T2D
• Z3
• H3
• A3 (H100)
• G4
• G2

Limitations for attaching Hyperdisk Throughput volumes to 4th-generation instances

If you create a Hyperdisk Throughput volume and attach it to a4th-generation instancelike C4, C4A, or N4, you can only attach that volume to other4th-generation instances.

If you attach a Hyperdisk Throughput volume to a 1st-, 2nd-, or 3rd-generation instance,you can't attach it to a 4th-generation instance. Conversely,you can't attach Hyperdisk Throughput volumes that were attached to 4th-generation instances to other instance types. In these scenarios, you must create a newHyperdisk Throughput volume from the existing Hyperdisk Throughput volume, then attach the new volumeto the instance.

For example, if you detach a Hyperdisk Throughput volume from a C4 instance, then you can't attachit to a G2 instance. You must create a new Hyperdisk Throughput volume.

To create a new Hyperdisk Throughput volume from an existing volume, follow the steps inChange the type, placement, or location of a disk,or use thegcloud convert command.

About provisioned performance

You don't have to provision performance when you createHyperdisk volumes. If you don't provision performance, Compute Enginecreates the volume with default values that you can modify later.For details about default values, seeDefault IOPS andthroughput values.

If you know your performance needs, you can specify IOPS and throughput limitsfor a Hyperdisk Throughput volume when you create the volume, and you can changethe provisioned values after you create the volume. You can't specify anIOPS or throughput level if you don't specify a size.

Important: Hyperdisk volumescan't reach the provisioned performance unless the compute instance supports thatlevel of performance. For detailed performance limits for all supported instancesby machine type, seePerformance limits when attached toan instance.

Size and performance limits

The following limits apply to the size and throughput values you can specify fora Hyperdisk Throughput volume.

• Size: 2 TiB-32 TiB.The default size is 2 TiB.
• Throughput: 20-2,400 MiB/s,with the following restrictions:
  • Minimum throughput: provisioned throughput must be at least10 times the volume's size in TiB.
  • Maximum throughput: provisioned throughput can be at most 90times the volume's size in TiB, up to a maximum 2,400 MiB/s.For examples, seeLimits for provisioned throughput.
• IOPS: you can't specify an IOPS limit for Hyperdisk Throughput volumes. Instead, the provisioned IOPSdepends on the provisioned throughput. Each Hyperdisk Throughput volume is provisioned with4 IOPS for each MiB/s of throughput, up to a maximum of9,600 IOPS.

Limits for provisioned throughput

The following table lists the limits for configurable throughput for common volume sizes.If a size isn't listed, use the following formula to calculate the allowablevalues, wherex is the volume's size in TiB:

• Minimum configurable throughput:10x
• Maximum configurable throughput:MIN (90x, 2400)

Size (TiB)	Minimum throughput (MiB/s)	Maximum throughput (MiB/s)
2	20	180
5	50	450
10	100	900
27	270	2,400
32	320	2,400

Default size, IOPS, and throughput values

If you don't specify a size or throughput value when you create a Hyperdisk Throughput volume,Compute Engine assigns default values.

The default size for Hyperdisk Throughput volumes is 2 TiB.

The default throughput and IOPS are based on the following formulas,wherex is the volume's size in TiB.

• Default throughput:MIN (90x, 2400) MiB/s
• Default IOPS:4t, wheret is the default throughput.You can't directly configure the IOPS level.

Change the provisioned performance or size

You can change the provisioned size every 6 hours and itsthroughput every 4 hours. To learn how to modifysize or performance, seeModify a Hyperdisk volume.

Performance limits when attached to an instance

This section lists the performance limits for Hyperdisk Throughput. You can specify up to 2,400 MiB/sof throughput for a single Hyperdisk Throughput volume. You can't provision an IOPSlevel, but each MiB/s of provisioned throughput comes with 4IOPS, up to 9,600 IOPS.

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.

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.

Disaster protection for Hyperdisk Throughput volumes

You can back up a Hyperdisk Throughput volume withstandard snapshots.Snapshots back up the data on a Hyperdisk Throughput volume at a specific point in time.

Cross-zonal replication

You can't replicate Hyperdisk Throughputvolumes to another zone. To replicate data to another zone within the same region,you must useHyperdisk Balanced High Availability volumes.

Regional availability for Hyperdisk Throughput

Hyperdisk Throughput is available in all zones and regions.

Hyperdisk Throughput Storage Pools

You can use Hyperdisk Throughput Storage Pools to simplify planning, avoid overprovisioning storage,and reduce costs. Hyperdisk Throughput Storage Pools let you to purchase Hyperdisk Throughput storage inbulk. To learn more, seeAbout Hyperdisk Storage Pools.

Pricing

You're billed for the total provisioned size and throughput of your Hyperdisk Throughputvolumes until you delete them. You incur charges even if the volume isn'tattached to any instances or if the instance is suspended or stopped. For moreinformation, seeDisk pricing.

Limitations

• Hyperdisk Throughput volumes are zonal and can only be accessed from the zone where the volume was created.
• You can't create amachine image from aHyperdisk Throughput volume.
• You can't create an instant snapshot from a Hyperdisk Throughput volume.
• You can't use Hyperdisk Throughput volumes as boot disks.
• You can change a Hyperdisk Throughput volume's size every 6 hours.You can change its throughput every 4 hours.
• To use Hyperdisk Throughput with N4, C4, or C4A instances, see theLimitations for attaching Hyperdisk Throughput volumes to N4, C4, or C4A instances.

What's next

• Add a Hyperdisk Throughput volume to your VM
• Learn aboutHyperdisk Storage Pools