Hyperdisk ボリュームの読み取りと書き込みには、VM の CPU サイクルが必要です。VM インスタンスの CPU が不足していると、前述の IOPS をアプリケーションで管理することはできません。非常に高い安定した IOPS レベルを実現するには、I/O の処理に CPU の空きが必要です。
Hyperdisk のパフォーマンス指標を確認する
ディスクのパフォーマンス指標は、Google Cloudの統合モニタリング ソリューションである Cloud Monitoring で確認できます。これらの指標を使用して、さまざまなアプリケーション ワークロードでディスクと他の VM リソースのパフォーマンスをモニタリングできます。
[[["わかりやすい","easyToUnderstand","thumb-up"],["問題の解決に役立った","solvedMyProblem","thumb-up"],["その他","otherUp","thumb-up"]],[["わかりにくい","hardToUnderstand","thumb-down"],["情報またはサンプルコードが不正確","incorrectInformationOrSampleCode","thumb-down"],["必要な情報 / サンプルがない","missingTheInformationSamplesINeed","thumb-down"],["翻訳に関する問題","translationIssue","thumb-down"],["その他","otherDown","thumb-down"]],["最終更新日 2025-08-18 UTC。"],[[["\u003cp\u003eHyperdisk volumes may require performance tuning after provisioning to meet specific application and operating system needs.\u003c/p\u003e\n"],["\u003cp\u003eUtilizing a high I/O queue depth is essential for achieving the high IOPS and throughput capabilities of network-attached Hyperdisk volumes, with the recommended depth varying based on desired performance levels.\u003c/p\u003e\n"],["\u003cp\u003eSufficient free CPU cycles on the VM are necessary to manage the high IOPS associated with Hyperdisk volumes, ensuring consistent performance.\u003c/p\u003e\n"],["\u003cp\u003eCloud Monitoring and the console's Observability page allow you to review Hyperdisk performance metrics to observe the performance of disks and VM resources under different workloads.\u003c/p\u003e\n"]]],[],null,["Linux Windows\n\n*** ** * ** ***\n\nAfter you provision your Google Cloud Hyperdisk volumes, your application and operating system\nmight require performance tuning to meet your performance needs.\n\nIn the following sections, we describe a few key elements that can be tuned for\nbetter performance and how you can apply some of these elements to specific\ntypes of workloads.\n\nFor an overview of how Google Cloud Hyperdisk performance works, see\n[About Hyperdisk performance](/compute/docs/disks/hyperdisk-performance).\n\nUse a high I/O queue depth\n\nHyperdisk volumes have higher latency than locally attached disks such as local\nSSDs because they are network-attached devices. They can provide very high IOPS\nand throughput, but you need to make sure that enough I/O requests are done in\nparallel. The number of I/O requests done in parallel is referred to as the *I/O\nqueue depth*.\n\nThe following tables show the recommended I/O queue depth to ensure you can\nachieve a certain performance level. The tables use a slight\noverestimate of typical latency in order to show conservative\nrecommendations. The example assumes that you are using an I/O size of 16 KB.\n\n| **Desired IOPS** | **Queue depth** |\n|------------------|-----------------|\n| 500 | 1 |\n| 1,000 | 2 |\n| 2,000 | 4 |\n| 4,000 | 8 |\n| 8,000 | 16 |\n| 16,000 | 32 |\n| 32,000 | 64 |\n| 64,000 | 128 |\n| 100,000 | 200 |\n| 200,000 | 400 |\n| 320,000 | 640 |\n\n| **Desired throughput (MB/s)** | **Queue depth** |\n|-------------------------------|-----------------|\n| 8 | 1 |\n| 16 | 2 |\n| 32 | 4 |\n| 64 | 8 |\n| 128 | 16 |\n| 256 | 32 |\n| 512 | 64 |\n| 1,000 | 128 |\n| 1,200 | 153 |\n\nEnsure you have free CPUs\n\nReading and writing to Hyperdisk volumes requires CPU cycles from your VM. If\nyour VM instance is starved for CPU, your application won't be able to manage\nthe IOPS described earlier. To achieve very high, consistent IOPS levels, you\nmust have CPUs free to process I/O.\n\nReview Hyperdisk performance metrics\n\nYou can review disk performance metrics in\n[Cloud Monitoring](https://console.cloud.google.com/monitoring),\nGoogle Cloud's integrated monitoring solution. You can use these metrics\nto observe the performance of your disks and other VM resources under different\napplication workloads.\n\nTo learn more, see\n[Reviewing disk performance metrics](/compute/docs/disks/review-disk-metrics).\n\nYou can also use the **Observability** page in the console to [view the disk\nperformance metrics](/compute/docs/disks/analyze-iops-hyperdisk#viewing-performance-metrics).\n\nWhat's next\n\n- Learn about [Hyperdisk pricing](/compute/disks-image-pricing#hyperdisk).\n- [Analyze the provisioned IOPS for Hyperdisk volumes](/compute/docs/disks/analyze-iops-hyperdisk)."]]