Hyperdisk throughput and VM egress limits

[alexm2]

Writes to Persistent Disks count towards the egress limits for a VM: https://cloud.google.com/compute/docs/disks/optimizing-pd-performance#egress_caps_write_throughput

I assume this is also the case for Hyperdisks, but I can't find any documentation that says so.  Can anyone confirm?

[JuatonCJ]

Hi @alexm2,

Welcome to Google Cloud Community!

When creating or modifying a Hyperdisk volume, the values must stay within the specified minimum and maximum Hyperdisks limit per disk. If you're adjusting the size of a Hyperdisk volume attached to a VM, the new size cannot exceed the limits set for Hyperdisks limit per VM. Additionally, the provisioned IOPS and throughput for the volume must adhere to the guidelines provided in the section on IOPS and throughput provisioning for Hyperdisk.

Unlike Persistent Disk, where performance scales automatically with size, Hyperdisk allows you to directly provision performance. To do this, you select the desired performance level for each volume. Each individual volume is fully isolated in terms of performance, ensuring that it receives the specific performance allocated to it.

For Hyperdisk Throughput volumes, throughput doesn't automatically scale with the size of the volume or number of provisioned vCPUs. You must specify the throughput level you want for each Hyperdisk Throughput disk.

For more reference in Hyperdisk throughput please review the following documentations:

• About Google Cloud Hyperdisk
• Analyze the Throughput needed for your workload
• Analyze the provisioned IOPS and throughput for Hyperdisk volumes 

I hope the above information is helpful.