The IOPS numbers you are seeing is inline with your expectations. However, the ~ 80ms latency is high. Is that the average latency or the max ? Can your share the min, avg, max latencies observed. ? Further, a perfstat would help to drill down further to understand what is going on. A single slow EBS volume can bring down the overall performance.
With the upcomming COT support for R3 instances we expect much lower latencies when compared to m3 instances. However, in general, please note that COT platform is not appropriate for 100% write workloads. For write intensive workloads we recommend our NPS platform.
The ~80ms latency is maybe average. I got latency-number by "statistics" commnad, but I couldn't find detail of cifs latency from internal site or documents. > statistics start -object cifs -vserver svm_ntap1 -sample-id 1
I have already broken a test environment because there was a problem of the cost.
Therefore, I can't run perfstat. I welcome a release of R3 instance of COT.
But I want to know the reason that R3 instance resolves this write performance issue.
CPU and Network were not bottleneck in write performance, and there was not difference in performance by one disk and two disks.