Skip to content

Commit 4659285

Browse files
Merge pull request #286494 from b-ahibbard/vm
acronyms
2 parents 26f31f8 + 851444f commit 4659285

File tree

2 files changed

+6
-6
lines changed

2 files changed

+6
-6
lines changed

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

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ ms.service: azure-netapp-files
55
ms.topic: conceptual
66
author: b-hchen
77
ms.author: anfdocs
8-
ms.date: 08/20/2024
8+
ms.date: 09/10/2024
99
---
1010
# Performance FAQs for Azure NetApp Files
1111

@@ -14,20 +14,20 @@ This article answers frequently asked questions (FAQs) about Azure NetApp Files
1414
## What should I do to optimize or tune Azure NetApp Files performance?
1515

1616
You can take the following actions per the performance requirements:
17-
- Ensure that the Virtual Machine is sized appropriately.
17+
- Ensure the virtual machine (VM) is sized appropriately.
1818
- Enable Accelerated Networking for the VM.
1919
- Select the desired service level and size for the capacity pool.
2020
- Create a volume with the desired quota size for the capacity and performance.
2121

22-
There is no need to set accelerated networking for the network interface cards (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.
22+
There is no need to set accelerated networking for the network interface cards (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 VMs. Azure NetApp Files NICs are optimized by design.
2323

2424
## How do I monitor Azure NetApp Files volume performance
2525

2626
Azure NetApp Files volumes performance can be monitored through [available metrics](azure-netapp-files-metrics.md).
2727

28-
## How do I convert throughput-based service levels of Azure NetApp Files to IOPS?
28+
## How do I convert throughput-based service levels of Azure NetApp Files to input/output operations per second (IOPS)?
2929

30-
You can convert MB/s to IOPS by using the following formula:
30+
You can convert megabytes per seconds (MBps) to IOPS with this formula:
3131

3232
`IOPS = (MBps Throughput / KB per IO) * 1024`
3333

articles/virtual-desktop/store-fslogix-profile.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -23,7 +23,7 @@ The following tables compare the storage solutions Azure Storage offers for Azur
2323
|Platform service|Yes, Azure-native solution|Yes, Azure-native solution|No, self-managed|
2424
|Regional availability|All regions|[Select regions](https://azure.microsoft.com/explore/global-infrastructure/products-by-region/?products=netapp&regions=all&rar=true)|All regions|
2525
|Redundancy|Locally redundant/zone-redundant/geo-redundant/geo-zone-redundant|Locally redundant/zone-redundant [with cross-zone replication](../azure-netapp-files/cross-zone-replication-introduction.md)/geo-redundant [with cross-region replication](../azure-netapp-files/cross-region-replication-introduction.md)|Locally redundant/zone-redundant/geo-redundant|
26-
|Tiers and performance| Standard (Transaction optimized)<br>Premium<br>Up to max 100K IOPS per share with 10 GBps per share at about 3-ms latency|Standard<br>Premium<br>Ultra<br>Up to max 460K IOPS per volume with 4.5 GBps per volume at about 1 ms latency. For IOPS and performance details, see [Azure NetApp Files performance considerations](../azure-netapp-files/azure-netapp-files-performance-considerations.md) and [the FAQ](../azure-netapp-files/faq-performance.md#how-do-i-convert-throughput-based-service-levels-of-azure-netapp-files-to-iops).|Standard HDD: up to 500 IOPS per-disk limits<br>Standard SSD: up to 4k IOPS per-disk limits<br>Premium SSD: up to 20k IOPS per-disk limits<br>We recommend Premium disks for Storage Spaces Direct|
26+
|Tiers and performance| Standard (Transaction optimized)<br>Premium<br>Up to max 100K IOPS per share with 10 GBps per share at about 3-ms latency|Standard<br>Premium<br>Ultra<br>Up to max 460K IOPS per volume with 4.5 GBps per volume at about 1 ms latency. For IOPS and performance details, see [Azure NetApp Files performance considerations](../azure-netapp-files/azure-netapp-files-performance-considerations.md) and [the FAQ](../azure-netapp-files/faq-performance.md#how-do-i-convert-throughput-based-service-levels-of-azure-netapp-files-to-inputoutput-operations-per-second-iops).|Standard HDD: up to 500 IOPS per-disk limits<br>Standard SSD: up to 4k IOPS per-disk limits<br>Premium SSD: up to 20k IOPS per-disk limits<br>We recommend Premium disks for Storage Spaces Direct|
2727
|Capacity|100 TiB per share, Up to 5 PiB per general purpose account |100 TiB per volume, up to 12.5 PiB per NetApp account|Maximum 32 TiB per disk|
2828
|Required infrastructure|Minimum share size 1 GiB|Minimum capacity pool 2 TiB, min volume size 100 GiB|Two VMs on Azure IaaS (+ Cloud Witness) or at least three VMs without and costs for disks|
2929
|Protocols|SMB 3.0/2.1, NFSv4.1 (preview), REST|[NFSv3, NFSv4.1](../azure-netapp-files/azure-netapp-files-create-volumes.md), [SMB 3.x/2.x](../azure-netapp-files/azure-netapp-files-create-volumes-smb.md), [dual-protocol](../azure-netapp-files/create-volumes-dual-protocol.md)|NFSv3, NFSv4.1, SMB 3.1|

0 commit comments

Comments
 (0)