[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["很难理解","hardToUnderstand","thumb-down"],["信息或示例代码不正确","incorrectInformationOrSampleCode","thumb-down"],["没有我需要的信息/示例","missingTheInformationSamplesINeed","thumb-down"],["翻译问题","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC)：2025-08-17。"],[],[],null,["# Expected performance\n\nThis page provides details on Google Cloud NetApp Volumes performance, also known as\nvolume throughput.\n\nAbout volume throughput\n-----------------------\n\nThroughput is the amount of data that's read or written within a specified\ntimeframe. NetApp Volumes scales throughput limits in the\nfollowing ways:\n\n- For Standard, Premium, and Extreme service level volumes: the capacity of your\n volumes and the service level of the storage pool that the volume is assigned\n to.\n\n- For Flex service level volumes: the capacity of the storage pool. All volumes\n in a Flex storage pool share the performance of the pool.\n\nThroughput and IOPS\n-------------------\n\nI/O operations per second (IOPS) is determined by concurrency, latency, and\nblock size. You can determine the number of IOPS using the following formula:\n\n*IOPS = concurrency / latency*\n\nThe achieved throughput is a result of your workload parameters. You can\ndetermine the achieved throughput using the following formula:\n\n*throughput = IOPS \\* block size*\n\n### Throughput and IOPS\n\nThis example describes how throughput and IOPS can be calculated.\n\nThe File Explorer copies a large file from a local SSD to a 4 TiB Extreme\nvolume with a 512 MiBps throughput limit using a single-threaded copy\n(`concurrency = 1`). Assuming it uses a 128 KiB block size and the volume\nhas a latency of 0.5 ms, you can use the following formula to calculate the\nthroughput and IOPS:\n\n*IOPS = 1/0.0005s = 2000 IOPS*\n\n*Throughput = 2000 IOPS \\* 128 KiB = 256000 KiBps = 250 MiBps*\n\nIn this example, the File Explorer isn't capable of driving the throughput to\nreach the volume limit (512 MiBps). Additionally, if latency is one\nmillisecond, throughput drops by 50% because latency directly impacts\nsingle-threaded applications. To drive this volume to its maximum performance\npotential, use multi-threaded applications that provide higher concurrency.\n\nMaximum volume throughput and IOPS\n----------------------------------\n\n- For Standard, Premium, and Extreme service level volumes: the maximum volume\n throughput that a volume can sustain is determined by the volume capacity and\n the maximum throughput per GiB provisioned set for the service level of the\n assigned storage pool. You can increase or decrease the maximum throughput of\n your volume by changing the capacity of the volume or re-assigning it to a\n storage pool with a different service level.\n\n- For Flex service level volumes: all volumes in a Flex storage pool share the\n performance of the pool.\n\n - The Flex storage pool with default performance provides a throughput of\n 16 MiBps per TiB of pool capacity up to a maximum of 1.6 GiBps,\n and IOPS of 1024 per TiB of pool capacity up to a maximum of 60,000 IOPS.\n\n - The Flex custom performance storage pool is available with zonal Flex pools\n in selected regions and provides independent scaling of capacity,\n performance, and IOPS. You can provision throughput from 64 MiBps to a\n maximum of 5 GiBps in increments of 1 MiBps. Each MiBps\n provisioned throughput includes 16 IOPS. Additional IOPS beyond the included\n throughput of 16 IOPS can be provisioned as required up to a maximum of\n 160,000 IOPS. Custom performance is available only in select regions. For\n more information about available regions, see\n [Supported regions for Flex custom performance](/netapp/volumes/docs/discover/service-levels#supported_regions_for_flex_custom_performance).\n\nThe following table provides the maximum throughput per TiB provisioned for\nNetApp Volumes Flex, Standard, Premium, and Extreme service\nlevels.\n\nNetApp Volumes maximum volume throughput scales linearly with\nvolume or pool capacity until a volume or pool limit is reached. Adding\nadditional capacity beyond that limit doesn't improve volume throughput. For\nmore information, see [NetApp Volumes benchmarks](/netapp/volumes/docs/performance/performance-benchmarks).\n\nFor some workloads, the volume may be constrained before it reaches the maximum\nthroughput limit. Examine the workload profiles found in the Network File System\n(NFS) and Server Message Block (SMB) performance benchmarks to estimate the\nvolume throughput for your workload.\n\nVolume throughput example\n-------------------------\n\nAn example of a maximum volume throughput of a volume with the Premium service\nlevel and a capacity of 1,500 GiB would see a result of 93.75 MiBps.\nThis is because the maximum throughput scales linearly with the volume capacity\nuntil it reaches its limit. For this example we use the following formula:\n\n*1,500 GiB x 64 KiBps/GiB per 1,024 KiB/MiB*\n\nWhat's next\n-----------\n\n[Verify performance](/netapp/volumes/docs/performance/verify-performance)."]]
