Stay organized with collections Save and categorize content based on your preferences.
This document describes the features of Hyperdisk Throughput. Hyperdisk Throughput is best suited for cost-sensitive workloads, analytics workloads, and workloads that require less than 600 MiB/s of throughput.
For more information about Hyperdisk and the other Hyperdisk types, see About Hyperdisk.
You can specify up to 600 MiB/s of throughput for a single Hyperdisk Throughput volume. You can't provision an IOPS level, but each MiB/s of provisioned throughput comes with 4 IOPS, up to 2,400 IOPS.
Hyperdisk Throughput has a latency profile similar to hard-disk based storage, with average read latency of 10-30 milliseconds.
To create a new Hyperdisk Throughput volume, see Create a Hyperdisk volume.
Use casesHyperdisk Throughput is a good fit for the following use cases:
You can use Hyperdisk Throughput with the following machine series, however, C3-metal machine types aren't supported.
About provisioned performanceYou don't have to provision performance when you create Hyperdisk volumes. If you don't provision performance, Compute Engine creates the volume with default values that you can modify later. For details about default values, see Default IOPS and throughput values.
If you know your performance needs, you can specify IOPS and throughput limits for a Hyperdisk Throughput volume when you create the volume, and you can change the provisioned values after you create the volume. You can't specify an IOPS or throughput level if you don't specify a size.
Important:Hyperdisk volumes can't reach the provisioned performance unless the compute instance supports that level of performance. For detailed performance limits for all supported instances by machine type, see Performance limits when attached to an instance.
Size and performance limitsThe following limits apply to the size and throughput values you can specify for a Hyperdisk Throughput volume.
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 allowable values, where x is the volume's size in TiB:
10xMIN (90x, 600)If you don't specify an IOPS or throughput limit when you create a Hyperdisk Throughput volume, Compute Engine assigns default values. The assigned value is based on the following formulas, where x is the volume's size in TiB.
MIN (24x, 600) MiB/sYou can change the provisioned size every 6 hours and its throughput every 4 hours. To learn how to modify size or performance, see Modify a Hyperdisk volume.
Performance limits when attached to an instanceThis section lists the performance limits for Hyperdisk Throughput. You can specify up to 600 MiB/s of throughput for a single Hyperdisk Throughput volume. You can't provision an IOPS level, but each MiB/s of provisioned throughput comes with 4 IOPS, up to 2,400 IOPS.
The following table lists the maximum performance that Hyperdisk Throughput volumes can achieve for each supported instance. A Hyperdisk Throughput volume's performance when it's attached to an instance can't exceed the limits for the instance's machine type. The performance limits are also shared across all Hyperdisk Throughput volumes attached to the same instance, regardless of each volume's provisioned performance.
Achieve higher performance with multiple Hyperdisk Throughput volumesCertain instances can exceed the maximum performance for a single Hyperdisk Throughput volume —600 MiB/s. An instance can achieve these higher limits if you attach multiple Hyperdisk Throughput volumes to the instance.
If an instance's performance limit in the following table exceeds 600 MiB/s, then the instance can achieve that limit only if you attach multiple Hyperdisk Throughput volumes. For example, the performance limit for a c3-*-22 instance using Hyperdisk Throughput volumes is 1,200 MiB/s. Therefore, to achieve 1,200 MiB/s of throughput, you must attach at least two Hyperdisk Throughput volumes to the instance.
The performance limits also apply to custom N2 and N2D machine types.
Instance machine type Maximum throughput (MiB/s) Minimum number of disks neededa3-*-1g 1,200 2 a3-*-2g 2,400 4 a3-*-4g 2,400 4 a3-*-8g 3,000 5 c3-*-4 240 1 c3-*-8 800 2 c3-*-22 1,200 2 c3-*-44 1,800 3 c3-*-88 2,400 4 c3-*-176 2,400 4 c3-*-192 2,400 4 c3d-*-4 400 2 c3d-*-8 800 2 c3d-*-16 1,200 2 c3d-*-30 1,200 2 c3d-*-60 2,400 4 c3d-*-90 2,400 4 c3d-*-180 2,400 4 c3d-*-360 2,400 4 g2-standard-4 240 1 g2-standard-8 800 2 g2-standard-12 800 2 g2-standard-16 1,200 2 g2-standard-24 1,200 2 g2-standard-32 1,800 3 g2-standard-48 2,400 4 g2-standard-96 2,400 4 h3-standard-88 240 1 m3-*-32 1,800 3 m3-*-64 2,400 4 m3-*-128 2,400 4 n2-*-2 200 1 n2-*-4 240 1 n2-*-6 240 1 n2-*-8 800 2 Custom N2 machine types with 10-14 vCPUs,
n2-*-10 and n2-*-12 800 2 n2-*-16 1,200 2 Custom N2 machine types with 18-30 vCPUs,
n2-*-18, n2-*-24, and n2-*-30 1,200 2 n2-*-32 1,800 3 Custom N2 machine types with 36-44 vCPUs,
n2-*-36, n2-*-40, and n2-*-44 1,800 3 n2-*-48 2,400 4 Custom N2 machine types with 36-44 vCPUs,
n2-*-36, n2-*-40, and n2-*-44 2,400 4 n2-*-64 3,000 5 Custom N2 machine types with 68-76 vCPUs,
n2-*-68, n2-*-72, and n2-*-76 2,400 4 n2-*-80 2,400 4 n2-*-96 2,400 4 n2-*-128 2,400 4 n2d-*-2 200 1 n2d-*-4 240 1 n2d-*-8 800 2 n2d-*-16 1,200 2 n2d-*-32 1,800 3 n2d-*-48 2,400 4 n2d-*-64 2,400 4 n2d-*-80 2,400 4 n2d-*-96 2,400 4 n2d-*-128 2,400 4 n2d-*-224 2,400 4 t2d-*-1 200 1 t2d-*-2 200 1 t2d-*-4 240 1 t2d-*-8 800 2 t2d-*-16 1,200 2 t2d-*-32 1,800 3 t2d-*-48 2,400 4 t2d-*-60 2,400 4 z3-*-8
z3-*-14
z3-*-16 800 2 z3-*-22
z3-*-32 1,200 2 z3-*-44 1,800 3 z3-*-88
z3-*-176 2,400 4 Disaster protection for Hyperdisk Throughput volumes
You can back up a Hyperdisk Throughput volume with standard snapshots. Snapshots back up the data on a Hyperdisk Throughput volume at a specific point in time.
Cross-zonal replicationYou can't replicate Hyperdisk Throughput volumes to another zone. To replicate data to another zone within the same region, you must use Hyperdisk Balanced High Availability volumes.
Regional availability for Hyperdisk ThroughputHyperdisk Throughput is available in all zones and regions.
Hyperdisk Throughput Storage PoolsYou 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 in bulk. To learn more, see About Hyperdisk Storage Pools.
PricingYou're billed for the total provisioned size and throughput of your Hyperdisk Throughput volumes until you delete them. You incur charges even if the volume isn't attached to any instances or if the instance is suspended or stopped. For more information, see Disk pricing.
LimitationsExcept as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2025-07-02 UTC.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-07-02 UTC."],[],[]]
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4