Stay organized with collections Save and categorize content based on your preferences.
You can view the disk description to see the provisioned input/output operations per second (IOPS) or the provisioned throughput for Google Cloud Hyperdisk volumes.
You can change the provisioned IOPS or throughput once in every 4 hour period. Each change of the IOPS or throughput level is logged. You can review the log history and compare it with performance metrics to understand how the provisioned IOPS and throughput levels relate to the performance level observed by your workload.
Before you beginSelect the tab for how you plan to use the samples on this page:
ConsoleWhen you use the Google Cloud console to access Google Cloud services and APIs, you don't need to set up authentication.
gcloudInstall the Google Cloud CLI. After installation, initialize the Google Cloud CLI by running the following command:
gcloud init
If you're using an external identity provider (IdP), you must first sign in to the gcloud CLI with your federated identity.
Note: If you installed the gcloud CLI previously, make sure you have the latest version by runninggcloud components update.To use the REST API samples on this page in a local development environment, you use the credentials you provide to the gcloud CLI.
Install the Google Cloud CLI. After installation, initialize the Google Cloud CLI by running the following command:
gcloud init
If you're using an external identity provider (IdP), you must first sign in to the gcloud CLI with your federated identity.
For more information, see Authenticate for using REST in the Google Cloud authentication documentation.
To view the provisioned IOPS or throughput for your Hyperdisk volumes, view the disk information.
ConsoleIn the Google Cloud console, go to the Disks page.
Click the name of the disk to view the configuration details.
Use the gcloud compute disks describe command to view the disk details.
gcloud compute disks describe DISK_NAME \ --zone ZONE_NAME \ --format="text(name, provisionedIops, provisionedThroughput, sizeGb)"
Replace the following:
DISK_NAME: the name of the Hyperdisk volume.ZONE_NAME: the zone where the Hyperdisk volume was created.The output shows the name of the disk, the current disk size and the provisioned IOPS or throughput, for example:
name: my-hyperdisk-b provisionedIops: '8500' provisionedThroughput: '140' sizeGb: '150'
Construct a GET request to the compute.disks.get method. In the request body, specify the name of the Hyperdisk volume.
GET https://compute.googleapis.com/compute/v1/projects/PROJECT_ID/zones/ZONE/disks/DISK_NAME/get
Replace the following:
PROJECT_ID: your project ID.ZONE: the zone where your Hyperdisk volume is located.DISK_NAME: the name of the Hyperdisk volume to view.In the response body, you can view the current disk size, provisioned IOPS, and throughput, for example:
{
...
"name": "my-hyperdisk-x",
"physicalBlockSizeBytes": "4096",
"provisionedIops": "100000",
...
"sizeGb": "1000",
"status": "READY",
...
}
You can use a query filter to return only the information you want to view. To view only the fields shown in the preceding example output, append a query parameter similar to the following to your request.
?fields=name,physicalBlockSizeBytes,provisionedIops,provisionedThroughput,sizeGb,status
To view performance metrics for your VMs, use the Cloud Monitoring observability metrics available in the Google Cloud console.
In the Google Cloud console, go to the VM Instances page.
To view metrics for individual VMs:
Click the name of the VM you want to view performance metrics for. The VM Details page opens.
Click the Observability tab to open the Observability Overview page.
Explore the VM's performance metrics. The following are key metrics related to disk performance for a VM:
On the Overview page:
CPU Utilization. The percent of CPU used by the VM.
Network Traffic. The average rate of bytes sent and received in one minute intervals.
Disk Throughput. The average rate of bytes written to and read from disks.
Disk IOPS. The average rate of I/O read and write operations to disks.
On the Disks Performance page, view the following charts:
Operations (IOPS). The average rate of I/O read and write operations to the disk in one-minute time periods.
IOPS by Storage Type The average rate of I/O operations to the disk in one-minute time periods, grouped by the storage type and device type.
Throughput (MB/s) The average rate of bytes written to and read from the VM's disks in one-minute time periods.
Throughput by Storage Type The average rate of bytes written to and read from the VM's disks in one-minute time periods, grouped by the storage type and device type.
I/O Size Avg. The average size of I/O read and write operations to disks. Small (4 to 16 KiB) random I/O operations are usually limited by IOPS and sequential or large (256 KiB-1 MiB) I/O operations are usually limited by throughput.
Queue Length Avg. The number of queued and running disk I/O operations, also called queue depth, for the top 5 devices. To reach the performance limits of your Hyperdisk and Persistent Disk volumes, use a high I/O queue depth.
I/O Latency Avg. The average latency of I/O read and write operations aggregated across operations of all block storage devices attached to the VM, measured by the Ops Agent in the VM. This value includes operating system and file system processing time.
To determine the IOPS needed for your workload, make note of the peak and average IOPS and throughput rates during times of peak usage, and also during a normal workload cycle, to get an idea of your workload requirements.
Observe the IOPS requirements of your workload using any of the following methods:
Based on the observed metric values, determine if you should adjust the provisioned IOPS for your VM. For example:
You can provision throughput separately from disk capacity for the following Hyperdisk types:
You can specify the target throughput level for a given volume. Individual volumes have full performance isolation - each volume gets the performance provisioned to it. However, the throughput is ultimately capped by per-VM limits for the VM to which your volumes are attached. To review these limits, see Hyperdisk performance limits.
Both read and write operations count against the throughput limit provisioned for a Hyperdisk volume. The provisioned throughput and the maximum limits apply to the combined total of read and write throughput.
Observe the throughput requirements of your workload using any of the following methods:
If the total throughput provisioned for one or more Hyperdisk volumes exceeds the total throughput available at the VM level, the performance is limited to the VM-level performance.
What's nextExcept 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-07 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-07 UTC."],[[["You can review the provisioned input/output operations per second (IOPS) and throughput for Google Cloud Hyperdisk volumes, which can be changed once every 4 hours with each change being logged."],["To view Hyperdisk performance settings, you can use the Google Cloud console's Disks page, the `gcloud compute disks describe` command, or a REST API `compute.disks.get` request."],["VM performance metrics, including CPU utilization, network traffic, disk throughput, and disk IOPS, are available on the Observability tab of the VM Details page in the Google Cloud console."],["To determine the optimal IOPS and throughput for your workload, you should monitor peak and average usage patterns, adjusting the provisioned levels based on whether performance is exceeding or falling short of requirements."],["Hyperdisk Balanced and Hyperdisk Throughput allow you to provision throughput separately from disk capacity, but performance is capped by the per-VM limits of the VM to which the volumes are attached."]]],[]]
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