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 begin
-
If you haven't already, set up authentication.
Authentication is
the process by which your identity is verified for access to Google Cloud services and APIs.
To run code or samples from a local development environment, you can authenticate to
Compute Engine as follows.
Select the tab for how you plan to use the samples on this page:
Console
When you use the Google Cloud console to access Google Cloud services and APIs, you don't need to set up authentication.
gcloud
-
Install the Google Cloud CLI, then initialize it by running the following command:
gcloud init
- Set a default region and zone.
REST
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, then initialize it by running the following command:
gcloud init
-
View the provisioned performance settings for Hyperdisk
To view the provisioned IOPS or throughput for your Hyperdisk volumes, view the disk information.
Console
In the Google Cloud console, go to the Disks page.
Click the name of the disk to view the configuration details.
gcloud
Use the
gcloud compute disks describecommand to view the disk details.Hyperdisk Balanced
gcloud beta compute disks describe DISK_NAME \ --zone ZONE_NAME \ --format="text(name, provisionedIops, provisionedThroughput, sizeGb)"Hyperdisk Extreme
gcloud compute disks describe DISK_NAME \ --zone ZONE_NAME \ --format="text(name, provisionedIops, sizeGb)"Hyperdisk Throughput
gcloud compute disks describe DISK_NAME \ --zone ZONE_NAME \ --format="text(name, 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:
Hyperdisk Balanced
name: my-hyperdisk-b provisionedIops: '8500' provisionedThroughput: '140' sizeGb: '150'
Hyperdisk Extreme
name: my-hyperdisk-x provisionedIops: '100000' sizeGb: '1000'
Hyperdisk Throughput
name: my-hyperdisk-t provisionedThrougput: '300' sizeGb: '10000'
In the Google Cloud console, activate Cloud Shell.
At the bottom of the Google Cloud console, a Cloud Shell session starts and displays a command-line prompt. Cloud Shell is a shell environment with the Google Cloud CLI already installed and with values already set for your current project. It can take a few seconds for the session to initialize.
REST
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
For Hyperdisk Balanced (Preview), use the following command:
GET https://compute.googleapis.com/compute/beta/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
View disk performance metrics
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, do the following:
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.
I/O Size Avg. The average size of I/O read and write operations to disks. Small (4-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.
Analyze the IOPS needed for your workload
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:
- Use the Monitoring tab on the disk details page in the Google Cloud console.
- Use the Observability page for your VM, as described in View disk performance metrics.
Based on the observed metric values, determine if you should adjust the provisioned IOPS for your VM. For example:
- If the peak IOPS rate is close to the provisioned IOPS for the Hyperdisk volume, then you can try increasing the provisioned IOPS for the Hyperdisk volume to boost the performance of your application.
- If the peak IOPS rate is consistently lower than the provisioned IOPS, then you can lower the provisioned IOPS for the Hyperdisk volume to reduce the cost of the disk.
Analyze the Throughput needed for your workload
With Hyperdisk Balanced (Preview) and Hyperdisk Throughput, you can provision throughput separately from disk capacity. 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.
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 next
- Learn how to optimize Hyperdisk performance.
- Learn how to modify the settings for a Hyperdisk volume
- Learn about Hyperdisk pricing.