Summary
The combination of the quota assigned to the volume and the selected service level determines the throughput limit for a volume with automatic QoS. For volumes with manual QoS, the throughput limit can be defined individually.
Ensure you choose the correct service level and volume quota size for the expected performance level. Throughput limits are a combination of read and write speed.
The metrics used in analyzing the performance of Azure NetApp Files are:
- Average I/O Requests/second Corresponds to the sum of average Read I/O requests/second and average write I/O requests/second from the load profile section
- Average I/O MB/second Corresponds to the sum of average read I/O MB/second and average write I/O MB/second from the load profile section
- Average read latency Corresponds to the average latency of the Oracle Wait Event "db file sequential read" in microseconds
- Number of threads/schema Corresponds to the number of SLOB (Silly Little Oracle Benchmarks) threads per user schema
More resources
Visit Azure NetApp Files documentation to learn about performance best practices.
Learn more about performance benchmark testing done in Azure NetApp Files:
- Azure NetApp Files performance benchmarks for Linux
- Azure NetApp Files large volume performance benchmarks for Linux
- Performance impact of Kerberos on Azure NetApp Files NFSv4.1 volumes
- Oracle database performance on Azure NetApp Files single volumes
- Oracle database performance on Azure NetApp Files multiple volumes
- Azure NetApp Files datastore performance benchmarks for Azure VMware Solution
- Azure VMware Solution datastore performance considerations for Azure NetApp Files
- Performance considerations for Azure NetApp Files with cool access