Google Cloud Hyperdisk is a network block storage option offered on GKE. You can use this storage option in your GKE clusters in a similar way as with other Compute Engine Persistent Disk volumes with added flexibility to tune performance for your workload. Compared to Persistent Disk storage, Hyperdisk provides substantially higher maximum input/output operations per second (IOPS) and throughput. Unlike Persistent Disk volumes where performance is shared across all volumes attached to a node, with Hyperdisk, you can specify and tune the level of performance for each Hyperdisk volume.
You are billed for the total provisioned capacity of your Hyperdisk volumes until you delete them. You are charged per GiB per month. Additionally, you are billed for the following:
For pricing information, refer to Disk pricing in the Compute Engine documentation.
The following example shows how you can specify the nodeSelector property to control Pod scheduling on Autopilot clusters with the Performance Compute Class, when using Hyperdisk Balanced.
Use the following considerations to plan the right level of performance for your Hyperdisk volumes.
Hyperdisk BalancedWith Hyperdisk Balanced, you can provision capacity separately from throughput and IOPS. To provision throughput or IOPS, you select the level for a given volume. Individual volumes have full throughput isolation—each volume can use all the specified throughput or IOPS capacity for that volume. However, the throughput or IOPS is ultimately limited by per-instance limits on the VM instance to which your volumes are attached. To learn more about these limits, see Provisioned performance for Hyperdisk Balanced in the Compute Engine documentation.
Both read and write operations count against the throughput and IOPS limit provisioned for a Hyperdisk Balanced volume. The throughput or IOPS provisioned and the maximum limits apply to the combined total of read and write operations.
If the total throughput or IOPS provisioned for one or more Hyperdisk volumes exceeds the total throughput or IOPS available at the VM instance level, the performance is limited to the instance performance level.
Hyperdisk ThroughputWith Hyperdisk Throughput, you can provision capacity separately from throughput. To provision throughput, you select the level for a given volume. Individual volumes have full throughput isolation—each gets the throughput provisioned to it. However, the throughput is ultimately capped by per-instance limits on the VM instance to which your volumes are attached. To learn more about these limits, see About provisioned performance in the Compute Engine documentation. Both read and write operations count against the throughput limit provisioned for a Hyperdisk Throughput volume. The throughput provisioned and the maximum limits apply to the combined total of read and write throughput.
When defining a StorageClass, throughput provisioned for Hyperdisk Throughput volumes must follow these rules:
If the total throughput provisioned for one or more Hyperdisk Throughput volumes exceeds the total throughput available at the VM instance level, the throughput is limited to the instance throughput level.
Hyperdisk ExtremeWith Hyperdisk Extreme, you can provision capacity separately from the IOPS level. To provision the IOPS level, you specify the IOPS limit for a given volume. Individual volumes have full IOPS level isolation—each gets the IOPS level provisioned to it. However, the IOPS is ultimately capped by per-instance limits on the VM instance to which your volumes are attached. To learn more about these limits, see About provisioned performance in the Compute Engine documentation.
Both read and write operations count against the IOPS limit provisioned for a Hyperdisk Extreme volume. The IOPS provisioned, and the maximum limits listed in this document, apply to the total of read and write IOPS.
When defining a StorageClass, IOPS provisioned for Hyperdisk Extreme volumes must be no more than 350,000 IOPS, depending on the machine type.
If the total IOPS provisioned for one or more Hyperdisk Extreme volumes exceeds the total IOPS available at the VM instance level, the performance is limited to the instance IOPS level. If there are multiple Hyperdisk and Persistent Disk volumes attached to the same VM requesting IOPS at the same time, and the VM limits are reached, then each volume has an IOPS level proportional to their share in the total IOPS provisioned across all attached Hyperdisk Extreme volumes.
Hyperdisk MLWith Hyperdisk ML, you can provision capacity separately from performance. To provision performance, you select the throughput level for a given volume. Individual volumes have full performance isolation—each gets the performance provisioned to it.
When one volume is attached to multiple instances, the provisioned throughput will be dynamically distributed across instances. However, the throughput is ultimately capped by per-instance limits on the VM instance to which your volumes are attached.
Both read and write operations count against the throughput limits provisioned for a Hyperdisk ML volume when in READ-WRITE-SINGLE mode. The throughput provisioned and the maximum limits apply to the total of read and write throughput.
Throughput provisioned for Hyperdisk ML volumes must follow the following rules:
READ-ONLY-MANY mode, then the throughput value needs to be at least 100 MBps * number of instances attached.If the total throughput provisioned for one or more Hyperdisk ML volumes exceeds the total throughput available at the instance level, the performance will be limited to the instance-level performance.
Hyperdisk Balanced HAWith Hyperdisk Balanced High Availability, you can provision capacity separately from throughput and IOPS. To provision throughput or IOPS, you select the level of throughput and IOPS for a given volume. Individual volumes have full throughput isolation—each volume can use all the specified throughput or IOPS capacity for that volume. However, the throughput or IOPS is ultimately limited by per-instance limits on the VM instance to which your volumes are attached. To learn more about these limits, see About Google Cloud Hyperdisk in the Compute Engine documentation.
Both read and write operations count against the throughput and IOPS limit that's provisioned for a Hyperdisk Balanced High Availability volume. The provisioned throughput or IOPS and the maximum limits apply to the combined total of read and write operations.
If the total throughput or IOPS that are provisioned for one or more Hyperdisk volumes exceeds the total throughput or IOPS available at the VM instance level, the performance is limited to the instance-level performance.
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