Testing reveals a single cloud volume multi GCE instance upper limit of roughly 240,000 IOPS. These data points were generated based on the results of multiple Vdbench runs from fifteen GCE instances. The results are indicative of the performance a customer could expect to achieve against a single volume from applications run in a scale out (multiple compute node) configuration.
The sequential tests were done using the tools and configuration as procedures as above. In this case the maximum amount of throughput achievable against a single volume is ~3.4GiBps for both 100% reads and mixed 50% read/write workloads.
Testing reveals that the Cloud Volumes Service performs at minimal latency on GC. Running in the us-central1 region, NFSv3 workloads drove ~168,000 IOPS before reaching the 2ms latency mark.
Read this blog for more information on how enterprise applications perform with Cloud Volumes Service for Google Cloud Platform.
The table on the right pulls results generated during the testing for NFSv3 workload on Cloud Volumes Service for GC and information on Cloud Filestore listed by Google Cloud. Cloud Filestore enables customers to run smaller workloads they never thought possible in the cloud at a very low latency. Now, with the close partnership of NetApp and Google Cloud customers can also run their extremely demanding workloads at a low latency with Cloud Volumes Service for Google Cloud Platform!
Testing shows that when run against 15 n1-highcpu-16 GCE instances, a single cloud volume has an upper limit of roughly 306,000 IOPS in us-central1.
The same method was used to run sequential tests where the throughput reached ~3.1GiBps. However, the maximum amount of throughput that’s possible to generate against a single project is 3.3GiBps.
Windows applications can take advantage of excellent network latency across the board in Google Cloud. Testing shows that the us-central1 region achieved ~122,000 IOPS under 2ms latency whereas ~150,000 IOPS just pass the 2ms point.