Skip to content

Commit 0c802b6

Browse files
committed
performance faqs
1 parent a527513 commit 0c802b6

File tree

2 files changed

+15
-4
lines changed

2 files changed

+15
-4
lines changed

articles/azure-netapp-files/azure-netapp-files-performance-considerations.md

Lines changed: 11 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -32,15 +32,15 @@ The same empirical throughput ceiling applies to volumes with manual QoS. The ma
3232

3333
## Automatic QoS volume quota and throughput
3434

35-
This section describes quota management and throughput for volumes with the automatic QoS type.
35+
Learn about quota management and throughput for volumes with the automatic QoS type.
3636

3737
### Overprovisioning the volume quota
3838

39-
If a workload’s performance is throughput-limit bound, it is possible to overprovision the automatic QoS volume quota to set a higher throughput level and achieve higher performance.
39+
If a workload’s performance is throughput-limit bound, it's possible to overprovision the automatic QoS volume quota to set a higher throughput level and achieve higher performance.
4040

41-
For example, if an automatic QoS volume in the Premium storage tier has only 500 GiB of data but requires 128 MiB/s of throughput, you can set the quota to 2 TiB so that the throughput level is set accordingly (64 MiB/s per TB * 2 TiB = 128 MiB/s).
41+
For example, if an automatic QoS volume in the Premium storage tier has only 500 GiB of data but requires 128 MiB/s of throughput, you can set the quota to 2 TiB so the throughput level is set accordingly (64 MiB/s per TB * 2 TiB = 128 MiB/s).
4242

43-
If you consistently overprovision a volume for achieving a higher throughput, consider using the manual QoS volumes or using a higher service level instead. In this example, you can achieve the same throughput limit with half the automatic QoS volume quota by using the Ultra storage tier instead (128 MiB/s per TiB * 1 TiB = 128 MiB/s).
43+
If you consistently overprovision a volume for achieving a higher throughput, consider using the manual QoS volumes or using a higher service level instead. In this example, you can achieve the same throughput limit with half the automatic QoS volume quota by using the Ultra storage tier instead (128 MiB/s per TiB * 1 TiB = 128 MiB/s).
4444

4545
### Dynamically increasing or decreasing volume quota
4646

@@ -62,6 +62,13 @@ If your performance requirements are temporary in nature, or if you have increas
6262

6363
If you use manual QoS volumes, you don’t have to overprovision the volume quota to achieve a higher throughput because the throughput can be assigned to each volume independently. However, you still need to ensure that the capacity pool is pre-provisioned with sufficient throughput for your performance needs. The throughput of a capacity pool is provisioned according to its size and service level. See [Service levels for Azure NetApp Files](azure-netapp-files-service-levels.md) for more details.
6464

65+
## Monitoring volumes for performance
66+
67+
Azure NetApp Files volumes can be monitored using available [Performance metrics](azure-netapp-files-metrics.md#performance-metrics-for-volumes).
68+
69+
When volume throughput reaches its maximum (as determined by the QoS setting), the volume response times (latency) increase. This effect can be incorrectly perceived as a performance issue caused by the storage. Increasing the volume QoS setting (manual QoS) or increasing the volume size (auto QoS) increases the allowable volume throughput.
70+
71+
To check if the maximum throughput limit has been reached, monitor the metric [Throughput limit reached](azure-netapp-files-metrics.md#volumes). For more recommendations, see [Performance FAQs for Azure NetApp Files](faq-performance.md#what-should-i-do-to-optimize-or-tune-azure-netapp-files-performance).
6572

6673
## Next steps
6774

articles/azure-netapp-files/faq-performance.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -21,6 +21,10 @@ You can take the following actions per the performance requirements:
2121

2222
There is no need to set accelerated networking for the NICs in the dedicated subnet of Azure NetApp Files. [Accelerated networking](../virtual-network/virtual-machine-network-throughput.md) is a capability that only applies to Azure virtual machines. Azure NetApp Files NICs are optimized by design.
2323

24+
## How do I monitor Azure NetApp Files volume performance
25+
26+
Azure NetApp Files volumes performance can be monitored through [available metrics](azure-netapp-files-metrics.md).
27+
2428
## How do I convert throughput-based service levels of Azure NetApp Files to IOPS?
2529

2630
You can convert MB/s to IOPS by using the following formula:

0 commit comments

Comments
 (0)