| title | Performance FAQs for Azure NetApp Files |
|---|---|
| description | Answers frequently asked questions (FAQs) about Azure NetApp Files Performance. |
| ms.service | azure-netapp-files |
| ms.topic | concept-article |
| author | b-hchen |
| ms.author | anfdocs |
| ms.date | 09/10/2024 |
This article answers frequently asked questions (FAQs) about Azure NetApp Files Performance.
You can take the following actions per the performance requirements:
- Ensure the virtual machine (VM) is sized appropriately.
- Enable Accelerated Networking for the VM.
- Select the desired service level and size for the capacity pool.
- Create a volume with the desired quota size for the capacity and performance.
There is no need to set accelerated networking for the network interface cards (NICs) in the dedicated subnet of Azure NetApp Files. Accelerated networking is a capability that only applies to Azure VMs. Azure NetApp Files NICs are optimized by design.
Azure NetApp Files volumes performance can be monitored through available metrics.
How do I convert throughput-based service levels of Azure NetApp Files to input/output operations per second (IOPS)?
You can convert megabytes per seconds (MBps) to IOPS with this formula:
IOPS = (MBps Throughput / KB per IO) * 1024
You can change the service level of an existing volume by moving the volume to another capacity pool that uses the service level you want for the volume. See Dynamically change the service level of a volume.
Azure NetApp Files provides volume performance metrics. You can also use Azure Monitor for monitoring usage metrics for Azure NetApp Files. See Metrics for Azure NetApp Files for the list of performance metrics for Azure NetApp Files.
In the absence of other symptoms (such as errors, network issues, or an application not responding), low IOP workloads are typically not a problem. Low IOPS are typically below 500-600 IOPS but can vary.
Azure NetApp Files responds to requests as they come in. A workload with few requests might appear to be higher, but is responding as expected. Low IOPS workloads (for example 5 IOPS and 32 KiB/s):
- Aren't in the RAM cache, so need to go to disk more.
- Don't have a high sample size, so are considered statistically irrelevant.
- Don't have enough samples to average out any outliers.
Reported latency can reach the seconds or tens of seconds range due to the latency averaging skew. Increasing the workload on the volume with low IOPS can further help determine if latency skew is the reason the latency shows an inflated number.
See Performance impact of Kerberos on NFSv4.1 volumes for information about security options for NFSv4.1, the performance vectors tested, and the expected performance impact.
[!INCLUDE nconnect krb5 performance warning]
No, Azure NetApp Files does not support SMB Direct.
NIC Teaming isn't supported in Azure. Although multiple network interfaces are supported on Azure virtual machines, they represent a logical rather than a physical construct. As such, they provide no fault tolerance. Also, the bandwidth available to an Azure virtual machine is calculated for the machine itself and not any individual network interface.
Jumbo frames aren't supported with Azure virtual machines.
- Performance impact of Kerberos on NFSv4.1 volumes
- Performance considerations for Azure NetApp Files
- Performance benchmark test recommendations for Azure NetApp Files
- Performance benchmarks for Linux
- Performance impact of Kerberos on NFSv4.1 volumes
- How to create an Azure support request
- Networking FAQs
- Security FAQs
- NFS FAQs
- SMB FAQs
- Capacity management FAQs
- Data migration and protection FAQs
- Azure NetApp Files backup FAQs
- Application resilience FAQs
- Integration FAQs