This section describes the performance characteristics and default service limits of Azure Native Qumulo (ANQ) v2.
v2 introduces a file system architecture that offers improved performance and flexibility for file systems of any size. For this reason, we eliminated the concept of total available capacity. You pay only for the data you store and, separately, for the throughput you use.
- We describe the performance of your v2 instance in terms of throughput (bytes per second), IOPS, and operation latency.
- Because v2 is a distributed file system, it is very effective for servicing multi-stream workloads with multiple clients or threads. The throughput and IOPS for single-stream and low-concurrency workloads might be lower than the performance characteristics listed in this section.
Throughput Performance
v2 instances can perform at above 100 Gbps with high-concurrency, multi-stream workloads. However, when you provision an v2 instance, Qumulo sets a default service limit of about 4 GBps. If you have a workload that needs higher sustained or peak throughput peak, to raise this service limit.
The default service limit isn’t a hard cap. In certain scenarios, it might be possible to reach a throughput higher than 4 GBps with default configuration.
IOPS Performance
By default, v2 is optimized for high-throughput (rather than high-IOPS) workloads.
For workloads with IOPS sensitivity, for a technical consultation.