Our test indicates performance a customer could achieve with single or multiple clients against a single instance of Cloud Volumes Service for AWS. The test reveals that the maximum I/O that can drive from a single Cloud Volumes Service instance to a single client is ~60,000, whether 1K, 4K or 8K random read, and 50,000 down to ~40,000 for the writes. However, with multiple clients, a single instance of Cloud Volumes Service can provide more than 200k IOPS.
Our sequential test was done using the exact same tests and procedures. In this
For a deeper understanding of how to best run Cloud Volumes Service on AWS check out our 3 part blog series on the subject.
The graphs compare the performance when using EBS and when using NetApp Cloud Volumes Service for AWS. The graph on the right shows that Oracle is able to drive 250,000 file system IOPS at 2ms when using the c5.18xlarge instance and a single volume provisioned from the Cloud Volumes Service, or 144,000 file system operations at below 2ms using the c5.9xlarge.
The graph to the left provides more performance examples of how Oracle workloads behave on Cloud Volumes Service for AWS when
For more information on Oracle Performance and Storage Comparison in AWS: Cloud Volumes Service, EBS, EFS.
The graph to the right shows the performance of a MySQL workload running on c5.18xlarge. Run against the single Cloud Volumes Service instance, we were able to generate close to 25,000 IOPS at 4 ms latency, and 22,000 IOPS at 3 ms latency.
The graphs demonstrate how Cloud Volumes Service for AWS and EFS compare when running random and sequential workloads.
Elastic File System: Maximum 250/MB/s per instance throughput
Cloud Volumes: 1GB/s maximum per instance throughput (512MB/s read + 512MB/s write)
Elastic File System: Maximum 7,000 IOPS per volume (as documented by AWS)
Cloud Volumes: ~200,000 maximum IOPS per volume as tested