A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from http://cloud.google.com/compute/docs/disks/hd-types/hyperdisk-balanced below:

About Hyperdisk Balanced | Compute Engine Documentation

Skip to main content About Hyperdisk Balanced

Stay organized with collections Save and categorize content based on your preferences.

This document describes the features of Hyperdisk Balanced, the general-purpose Hyperdisk type. Hyperdisk Balanced is the best fit for most workloads and offers the best combination of price and performance for total cost of ownership. For more information about Hyperdisk and the other Hyperdisk types, see About Hyperdisk.

You can specify up to 160,000 IOPS and 2,400 MiB/s of throughput for a single Hyperdisk Balanced volume. Hyperdisk Balanced is designed for sub-millisecond latencies.

To create a new Hyperdisk Balanced volume, see Create a Hyperdisk volume.

Use cases

Hyperdisk Balanced is a good fit for most workloads, including the following use cases:

Machine series support

You can use Hyperdisk Balanced with the following machine series:

About provisioned performance for Hyperdisk Balanced

You 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 Balanced 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 limits

The following limits apply to the size, IOPS, and throughput values you can specify for a Hyperdisk Balanced volume.

Limits for provisioned IOPS

You can choose the IOPS limit for a Hyperdisk Balanced volume according to the following limits. The minimum and maximum limits vary by size.

To calculate the range of configurable IOPS values for a specific volume size, use these formulas:

The following table lists the limits for configurable IOPS for common volume sizes.

Size (GiB) Configurable IOPS values 4 2,000 5 2,500 10 3,000 to 5,000 50 3,000 to 25,000 150 3,000 to 75,000 319 3,000 to 159,500 320 or more 3,000 to 160,000 Limits for provisioned throughput

Volumes with 4 or 5 GiB of capacity have a fixed throughput value of 140 MiB/s. For larger volumes, you can provision additional throughput. The range of supported throughput values depends on the provisioned IOPS and is calculated with the following formulas, where P is the provisioned IOPS.

The following table lists the limits for some provisioned IOPS values and the corresponding throughput ranges. If a size isn't listed, use the preceding formula to calculate the allowable values.

Provisioned IOPS Configurable throughput (MiB/s) 2,000 140 to 500 2,500 140 to 625 3,000 140 to 750 4,000 140 to 1000 8,000 140 to 2000 32,000 140 to 2,400 50,000 156 to 2,400 64,000 250 to 2,400 150,000 585 to 2,400 160,000 625 to 2,400 Default size, IOPS, and throughput values

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

The default size for Hyperdisk Balanced volumes is 100 GiB.

The default IOPS and throughput are based on the following formulas, where x is the volume's size in GiB.

Baseline performance

Hyperdisk Balanced volumes include baseline, or free performance. The first 3,000 IOPS and 140 MiB/s of throughput that you provision for a volume are free. Performance you provision above the baseline amounts is billable performance, and is not free. If you provision a volume with 5,000 IOPS, you're billed for 2,000 IOPS. Similar principles apply to throughput.

Baseline performance is also included with Hyperdisk Balanced volumes that you create in the following Hyperdisk Storage Pools:

Hyperdisk Balanced volumes in Advanced performance Hyperdisk Storage Pools don't include baseline performance.

Baseline performance and quota

Baseline IOPS and throughput don't affect the IOPS and throughput quota for a project's Hyperdisk Balanced and Hyperdisk Balanced High Availability volumes.

For example, if your project has a quota of 500,000 IOPS and you create a Hyperdisk Balanced volume with 3,000 IOPS, then you still have a quota of 500,000 IOPS after you create the volume. If you also create a Hyperdisk Balanced High Availability volume with 4,000 IOPS, then the project would have a remaining IOPS quota of 499,000.

Limits for consuming baseline performance

A project's Hyperdisk Balanced and Hyperdisk Balanced High Availability volumes that are in the same zone can concurrently use up to 50 GiB/s of baseline throughput and up to 500,000 of baseline IOPS. This limit is referred to as the concurrent consumption limit for baseline performance.

The concurrent consumption limit for baseline performance restricts how much baseline performance the volumes can use at the same time, and doesn't affect much baseline performance you can provision. The concurrent consumption limit doesn't apply to consuming or provisioning billable performance.

For more information, see Concurrent consumption limits for baseline performance.

Change the provisioned performance or size

You can change the provisioned size of a Hyperdisk Balanced volume at most twice within a 4-hour window, and you can change the provisioned performance at most once every 4 hours. To learn how to modify size or performance, see Modify a Hyperdisk volume.

Performance limits when attached to an instance

This section lists the performance limits for each machine type that supports Hyperdisk Balanced. You can specify up to 160,000 IOPS and 2,400 MiB/s of throughput for a single Hyperdisk Balanced volume.

This section lists the maximum performance that Hyperdisk Balanced volumes can achieve for each supported instance. A Hyperdisk Balanced 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 Balanced volumes attached to the same instance, regardless of each volume's provisioned performance.

Achieve higher performance with multiple Hyperdisk Balanced volumes

Certain instances can exceed the maximum performance for a single Hyperdisk Balanced volume— 160,000 IOPS or 2,400 MiB per second (MiB/s). An instance can only achieve these higher limits if you attach multiple Hyperdisk Balanced volumes to the instance.

If an instance's performance limit in the following table exceeds 160,000 IOPS or 2,400 MiB/s, then the instance can only achieve that limit if you attach multiple Hyperdisk Balanced volumes. For example, the performance limit for a c4a-*-72 instance using Hyperdisk Balanced is 240,000 IOPS and 5,000 MiB/s. To achieve this maximum performance you must attach at least two Hyperdisk Balanced volumes to the instance.

Important: To reach the IOPS limits, you must use an I/O size of 4 KB. Maximum throughput limits require an I/O size of at least 256 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 reads and writes every second can't exceed 50,000.

The performance limits also apply to custom N4 machine types.

Instance machine type Maximum IOPS Maximum throughput (MiB/s) A3 a3-ultragpu-8g2 320,000 10,000 a3-megagpu-8g 160,000 4,800 a3-highgpu-1g 25,000 400 a3-highgpu-2g 120,000 1,800 a3-highgpu-4g 160,000 2,400 a3-highgpu-8g 160,000 4,800 a3-edgegpu-8g 160,000 4,800 A42 a4-highgpu-8g 320,000 10,000 A4X2 a4x-highgpu-4g 320,000 10,000 C3 c3-*-4 25,000 400 c3-*-8 50,000 800 c3-*-22 120,000 1,800 c3-*-44 160,000 2,400 c3-*-88 160,000 4,800 c3-*-176 160,000 10,000 c3-*-192 160,000 10,000 C3D c3d-*-4 25,000 400 c3d-*-8 50,000 800 c3d-*-16 75,000 1,200 c3d-*-30 75,000 1,200 c3d-*-60 160,000 2,400 c3d-*-90 160,000 2,400 c3d-*-180 160,000 2,400 c3d-*-360 160,000 2,400 C4 c4-*-22 50,000 400 c4-*-42 50,000 400 c4-*-82 50,000 800 c4-*-162 100,000 1,600 c4-*-242 100,000 1,600 c4-*-322 100,000 1,600 c4-*-482 160,000 2,400 c4-*-962 240,000 4,800 c4-*-1442 240,000 4,800 c4-*-1922 320,000 10,000 c4-*-2881,2 320,000 10,000 C4A c4a-*-1 25,000 400 c4a-*-2 50,000 800 c4a-*-4 50,000 800 c4a-*-8 50,000 1,000 c4a-*-16 60,000 1,600 c4a-*-32 120,000 2,400 c4a-*-48 160,000 3,300 c4a-*-64 240,000 4,400 c4a-*-72 240,000 5,000 C4D c4d-*-22 22,500 400 c4d-*-42 50,000 400 c4d-*-82 50,000 800 c4d-*-162 75,000 1,200 c4d-*-322 75,000 1,600 c4d-*-482 75,000 1,600 c4d-*-642 160,000 2,400 c4d-*-962 160,000 2,800 c4d-*-1922 240,000 4,800 c4d-*-3842 320,000 10,000 TPU v6e ct6e-standard-1t 75,000 1,200 ct6e-standard-4t 160,000 2,400 ct6e-standard-8t 160,000 2,400 G4 (Preview) g4-standard-48 75,000 1,600 g4-standard-96 160,000 2,800 g4-standard-192 240,000 4,800 g4-standard-384 320,000 10,000 H3 h3-standard-88 15,000 240 M1 m1-ultramem-40 60,000 1,200 m1-ultramem-80 100,000 2,400 m1-megamem-96 100,000 4,000 m1-ultramem-160 100,000 4,000 M2 m2-*-208 100,000 2,400 m2-*-416 100,000 4,000 M3 m3-*-32 160,000 2,400 m3-*-64 160,000 4,800 m3-*-128 160,000 4,800 M4 m4-*-562 160,000 2,400 m4-*-1122 240,000 4,800 m4-*-2242 320,000 10,000 N4 n4-*-2 15,000 240 n4-*-4 15,000 240 n4-*-6 15,000 240 n4-*-8 80,000 480 Custom N4 machine types with 10-14 vCPUs,
such as n4-*-10, n4-*-12, and n4-*-14 80,000 1,200 n4-*-16 80,000 1,200 Custom N4 machine types with 18-30 vCPUs,
such as n4-*-18, n4-*-24, and n4-*-30 80,000 1,200 n4-*-32 100,000 1,600 Custom N4 machine types with 34-46 vCPUs,
such as n4-*-34, n4-*-42, and n4-*-46 100,000 1,600 n4-*-48 160,000 2,400 Custom N4 machine types with 50-62 vCPUs,
such as n4-*-50, n4-*-58, and n4-*-62 160,000 2,400 n4-*-64 160,000 2,400 Custom N4 machine types with 66-78 vCPUs,
such as n4-*-66, n4-*-72, and n4-*-78 160,000 2,400 n4-*-80 160,000 2,400 X4 x4-*-9601 160,000 4,800 x4-*-14401 160,000 4,800 x4-*-19201 160,000 4,800 Z3 z3-*-8 50,000 800 z3-*-14
z3-*-16 100,000 1,600 z3-*-22 120,000 1,800 z3-*-32
z3-*-44 160,000 2,400 z3-*-88 160,000 4,800 z3-*-176 z3-*-1921 160,000 10,000 Includes bare metal instances.
Also offers steady state performance. For more information, see Performance limits for machine types with steady state performance.
Disaster recovery protection for Hyperdisk Balanced volumes

You can back up a Hyperdisk Balanced volume with instant snapshots and standard snapshots. Snapshots back up the data on a Hyperdisk Balanced volume at a specific point in time.

Replication across multiple regions

You can protect your data in the unlikely event of a regional outage by enabling Asynchronous Replication. Asynchronous Replication maintains a copy of the data on your volume in another region. For example, to protect a Hyperdisk Balanced volume in us-west1, you can use Asynchronous Replication to replicate the volume to a secondary volume in the us-east4 region. If the volume in us-west1 became unavailable, then you could use the secondary volume in us-east4.

Cross-zonal replication

You can't replicate Hyperdisk Balanced 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 Balanced

Hyperdisk Balanced is available in all zones and regions.

Hyperdisk Balanced Storage Pools

To simplify planning, avoid overprovisioning storage, and reduce costs, consider using Hyperdisk Balanced Storage Pools. Hyperdisk Balanced Storage Pools let you purchase Hyperdisk Balanced storage and performance in bulk. To learn more, see About Hyperdisk Storage Pools.

You can use multi-writer mode to attach a Hyperdisk Balanced volume to multiple instances, while each instance maintains write access. This feature enables high availability for workloads like Microsoft SQL Server Failover Cluster Infrastructure.

To learn more, see Share a disk between VMs.

Pricing

You are billed for the total provisioned size, IOPS, and throughput of your Hyperdisk Balanced volumes until you delete them. Charges incur even if the volume isn't attached to any instances or if the instance is suspended or stopped. For more information see Disk pricing.

Limitations for Hyperdisk Balanced What's next

Except 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-08-13 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-08-13 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