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-extreme below:

About Hyperdisk Extreme | Compute Engine Documentation

This document describes the features and performance limits of Hyperdisk Extreme volumes. Hyperdisk Extreme is designed for applications that require more than 160,000 IOPS or 2,400 MiB/s of bandwidth from a single volume, such as high-performance databases.

You can specify up to 350,000 IOPS for a single Hyperdisk Extreme volume. You can't provision a throughput level for Hyperdisk Extreme volumes. Each volume gets 250 MiB/s of throughput with every 1,000 IOPS, up to 5,000 MiB/s.

Hyperdisk Extreme volumes are designed for sub-millisecond latencies.

Use cases

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

Machine series support

You can use Hyperdisk Extreme with the following machine series:

Restrictions for machine series support About provisioned performance

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.

You can specify an IOPS limits for a Hyperdisk Extreme volume when you create the volume, and you can modify the provisioned IOPS after you create the volume. You can't specify an IOPS 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.

For details about performance for Hyperdisk volumes, see About Hyperdisk performance.

Size and performance limits

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

Limits for provisioned IOPS

The IOPS level you can specify for a Hyperdisk Extreme volume depends on the disk's size, according to the following formulas, where x is the volume's size in GiB.

This table provides the range of IOPS values that you can provision for common volume sizes. If a size value isn't listed, use the preceding formula to calculate the maximum allowable IOPS.

Volume size (GiB) Minimum IOPS Maximum IOPS 64 128 76,800 150 300 180,000 200 400 240,000 290 580 348,000 300 600 350,000 1,000 2,000 350,000 Default size, IOPS, and throughput values

If you don't specify a size or IOPS value when you create a Hyperdisk Extreme volume, Compute Engine provisions the volume with default values.

The default size is 1 TiB.

The default IOPS and throughput are based on the following formulas.

Change the provisioned IOPS or size

You can change the provisioned performance and size of a Hyperdisk Extreme volume at most once every 4 hours. For instructions on modifying size or performance, see Modify a Hyperdisk volume.

Performance limits when attached to an instance

This section lists the specific performance limits for each machine type that supports Hyperdisk Extreme. You can specify up to 350,000 IOPS for a single Hyperdisk Extreme volume. You can't provision a throughput level for Hyperdisk Extreme volumes. Each volume gets 250 MiB/s of throughput with every 1,000 IOPS, up to 5,000 MiB/s.

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

Achieve higher performance with multiple Hyperdisk Extreme volumes

Certain instances can exceed the maximum performance for a single Hyperdisk Extreme volume— 350,000 IOPS or 5,000  MiB/s. An instance can only achieve these higher limits if you attach multiple Hyperdisk Extreme volumes to the instance.

If an instance's performance limit in the following table exceeds 350,000 IOPS or 5,000  MiB/s, then the instance can only achieve that limit if you attach multiple Hyperdisk Extreme volumes. For example, the performance limit for a c3-*-176 instance using Hyperdisk Extreme is 500,000 IOPS and 10,000 MiB/s. To achieve this maximum performance you must attach at least two Hyperdisk Extreme volumes to the instance.

Important: 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. 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.

The performance limits also apply to custom machine types.

Instance machine type Maximum IOPS Maximum throughput (MiB/s) A3 a3-highgpu-4g 350,000 5,000 a3-ultragpu-8g2 500,000 10,000 a3-megagpu-8g 400,000 8,000 a3-highgpu-8g 400,000 8,000 a3-edgegpu-8g 400,000 8,000 A42 a4-highgpu-8g 500,000 10,000 A4X2 a4x-highgpu-4g 500,000 10,000 C3 c3-*-881 350,000 5,000 c3-*-1761 500,000 10,000 c3-*-1921,3 500,000 10,000 C3D c3d-*-601 350,000 5,000 c3d-*-901 350,000 5,000 c3d-*-1801 350,000 5,000 c3d-*-3601 350,000 5,000 C4 c4-*-962 350,000 5,000 c4-*-1442 350,000 5,000 c4-*-1922 500,000 10,000 c4-*-2882,3 500,000 10,000 C4A c4a-*-64 350,000 5,000 c4a-*-72 350,000 5,000 C4D c4d-*-642 350,000 5,000 c4d-*-962 350,000 5,000 c4d-*-1922 350,000 5,000 c4d-*-3842 500,000 10,000 G4 (Preview) g4-standard-96 350,000 5,000 g4-standard-192 350,000 5,000 g4-standard-384 500,000 10,000 M2 m2-*-208 100,000 4,000 m2-*-416 100,000 4,000 M3 m3-*-641 350,000 5,000 m3-*-1281 450,000 7,200 M4 m4-*-1122 350,000 5,000 m4-*-2242 500,000 10,000 N2 n2-*-801 160,000 5,000 n2-*-96 160,000 5,000 n2-*-128 160,000 5,000 X4 x4-*-9601,3 400,000 10,000 x4-*-14401,3 400,000 10,000 x4-*-19201,3 400,000 10,000 Z3 z3-*-881 350,000 5,000 z3-*-1761 350,000 5,000 z3-*-1921,3 500,000 10,000 If using Hyperdisk Extreme with an instance that uses Microsoft Windows, refer to the known issues for Windows VM instances.
Also offers steady state performance. For more information, see Performance limits for machine types with steady state performance.
Includes bare metal instances.
Disaster protection for Hyperdisk Extreme volumes

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

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 Extreme 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 Extreme 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 Extreme

Hyperdisk Extreme is available in all zones and regions.

Limitations

Hyperdisk Extreme volumes have the following limitations:

What's next

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