Skip to content

Commit fa8f5bb

Browse files
author
julie.chen
committed
adding SMB Performance FAQs article
1 parent ee9c008 commit fa8f5bb

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

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

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -24,7 +24,7 @@ This article answers frequently asked questions (FAQs) about SMB performance bes
2424

2525
Yes, SMB Multichannel is enabled by default, a change put in place in early January 2020. All SMB shares pre-dating existing SMB volumes have had the feature enabled, and all newly created volumes will also have the feature enabled at time of creation.
2626

27-
Any SMB connection established prior to the feature enablement will need to be reset to take advantage of the SMB Multichannel functionality. To reset, simply disconnect and reconnect the SMB share.
27+
Any SMB connection established prior to the feature enablement will need to be reset to take advantage of the SMB Multichannel functionality. To reset, you can disconnect and reconnect the SMB share.
2828

2929
## Does Azure NetApp Files support receive-side-scaling (RSS)?
3030

@@ -74,7 +74,7 @@ The command `netstat -na | findstr 445` proved that additional connections were
7474

7575
![Random I/O tests](../media/azure-netapp-files/azure-netapp-files-random-io-tests.png)
7676

77-
Note that the Azure virtual machine does not affect SMB (nor NFS) storage I/O limits. As shown below, the D16 instance type has a limited rate of 32,000 for cached storage IOPS and 25,600 for uncached storage IOPS. However, the graph above shows significantly more I/O over SMB.
77+
The Azure virtual machine does not affect SMB (nor NFS) storage I/O limits. As shown below, the D16 instance type has a limited rate of 32,000 for cached storage IOPS and 25,600 for uncached storage IOPS. However, the graph above shows significantly more I/O over SMB.
7878

7979
![Random I/O comparison](../media/azure-netapp-files/azure-netapp-files-random-io-tests-list.png)
8080

@@ -84,7 +84,7 @@ Tests similar to the random I/O tests described above were performed with 64-KiB
8484

8585
![Sequential I/O tests](../media/azure-netapp-files/azure-netapp-files-sequential-io-tests.png)
8686

87-
Note that Azure places network rate limits on each virtual machine type/size. The rate limit is imposed on outbound traffic only. The number of NICs present on a virtual machine has no bearing on the total amount of bandwidth available to the machine. For example, the D16 instance type has an imposed network limit of 8000 Mibps (1,000 MiB/s). As the sequential graph above shows, the limit affects the outbound traffic (writes) but not multichannel reads.
87+
Azure places network rate limits on each virtual machine type/size. The rate limit is imposed on outbound traffic only. The number of NICs present on a virtual machine has no bearing on the total amount of bandwidth available to the machine. For example, the D16 instance type has an imposed network limit of 8000 Mibps (1,000 MiB/s). As the sequential graph above shows, the limit affects the outbound traffic (writes) but not multichannel reads.
8888

8989
![Sequential I/O comparison](../media/azure-netapp-files/azure-netapp-files-sequential-io-tests-list.png)
9090

0 commit comments

Comments
 (0)