You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/storage/files/smb-performance.md
+40-21Lines changed: 40 additions & 21 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
---
2
2
title: Improve SMB Azure file share performance
3
-
description: Learn about ways to improve performance and throughput for premium SMB Azure file shares, including SMB Multichannel and metadata caching.
3
+
description: Learn about ways to improve performance and throughput for SSD (premium) SMB Azure file shares, including SMB Multichannel and metadata caching.
4
4
author: khdownie
5
5
ms.service: azure-file-storage
6
6
ms.topic: conceptual
@@ -11,15 +11,22 @@ ms.custom: references_regions
11
11
12
12
# Improve performance for SMB Azure file shares
13
13
14
-
This article explains how you can improve performance for premium SMB Azure file shares, including using SMB Multichannel and metadata caching (preview).
14
+
This article explains how you can improve performance for SSD (premium) SMB Azure file shares, including using SMB Multichannel and metadata caching.
15
15
16
16
## Applies to
17
17
18
-
| File share type | SMB | NFS |
19
-
|-|:-:|:-:|
20
-
| Standard file shares (GPv2), LRS/ZRS |||
21
-
| Standard file shares (GPv2), GRS/GZRS |||
@@ -28,20 +35,20 @@ The following tips might help you optimize performance:
28
35
- Ensure that your storage account and your client are co-located in the same Azure region to reduce network latency.
29
36
- Use multi-threaded applications and spread load across multiple files.
30
37
- Performance benefits of SMB Multichannel increase with the number of files distributing load.
31
-
-Premium share performance is bound by provisioned share size (IOPS/egress/ingress) and single file limits. For details, see [Understanding provisioning for premium file shares](understanding-billing.md#provisioned-v1-model).
32
-
- Maximum performance of a single VM client is still bound to VM limits. For example, [Standard_D32s_v3](/azure/virtual-machines/dv3-dsv3-series) can support a maximum bandwidth of 16,000 MBps (or 2GBps), egress from the VM (writes to storage) is metered, ingress (reads from storage) is not. File share performance is subject to machine network limits, CPUs, internal storage available network bandwidth, IO sizes, parallelism, as well as other factors.
38
+
-SSD (premium) share performance is bound by provisioned share size (IOPS/egress/ingress) and single file limits. For details, see [Understanding provisioning for premium file shares](understanding-billing.md#provisioned-v1-model).
39
+
- Maximum performance of a single VM client is still bound to VM limits. For example, [Standard_D32s_v3](/azure/virtual-machines/dv3-dsv3-series) can support a maximum bandwidth of 16,000 MBps (or 2GBps), egress from the VM (writes to storage) is metered. Ingress (reads from storage) is not. File share performance is subject to machine network limits, CPUs, internal storage available network bandwidth, IO sizes, parallelism, and other factors.
33
40
- The initial test is usually a warm-up. Discard the results and repeat the test.
34
41
- If performance is limited by a single client and workload is still below provisioned share limits, you can achieve higher performance by spreading load over multiple clients.
35
42
36
43
### The relationship between IOPS, throughput, and I/O sizes
37
44
38
45
**Throughput = IO size * IOPS**
39
46
40
-
Higher I/O sizes drive higher throughput and will have higher latencies, resulting in a lower number of net IOPS. Smaller I/O sizes will drive higher IOPS, but will result in lower net throughput and latencies. To learn more, see [Understand Azure Files performance](understand-performance.md).
47
+
Higher I/O sizes drive higher throughput and will have higher latencies, resulting in a lower number of net IOPS. Smaller I/O sizes drive higher IOPS, but will result in lower net throughput and latencies. To learn more, see [Understand Azure Files performance](understand-performance.md).
41
48
42
49
## SMB Multichannel
43
50
44
-
SMB Multichannel enables an SMB client to establish multiple network connections to an SMB file share. Azure Files supports SMB Multichannel on premium file shares for Windows clients. On the service side, SMB Multichannel is now enabled by default for all newly created storage accounts in all Azure regions. There's no additional cost for enabling SMB Multichannel.
51
+
SMB Multichannel enables an SMB client to establish multiple network connections to an SMB file share. Azure Files supports SMB Multichannel on SSD (premium) file shares for Windows clients. On the service side, SMB Multichannel is now enabled by default for all newly created storage accounts in all Azure regions. There's no other cost for enabling SMB Multichannel.
45
52
46
53
### Benefits
47
54
@@ -56,7 +63,7 @@ SMB Multichannel enables clients to use multiple network connections that provid
56
63
-**Automatic configuration**:
57
64
When SMB Multichannel is enabled on clients and storage accounts, it allows for dynamic discovery of existing connections, and can create addition connection paths as necessary.
58
65
-**Cost optimization**:
59
-
Workloads can achieve higher scale from a single VM, or a small set of VMs, while connecting to premium shares. This could reduce the total cost of ownership by reducing the number of VMs necessary to run and manage a workload.
66
+
Workloads can achieve higher scale from a single VM, or a small set of VMs, while connecting to SSD (premium) shares. This could reduce the total cost of ownership by reducing the number of VMs necessary to run and manage a workload.
60
67
61
68
To learn more about SMB Multichannel, refer to the [Windows documentation](/azure-stack/hci/manage/manage-smb-multichannel).
62
69
@@ -66,7 +73,7 @@ This feature provides greater performance benefits to multi-threaded application
66
73
67
74
SMB Multichannel for Azure file shares currently has the following restrictions:
68
75
69
-
- Only available for premium Azure file shares. Not available for standard Azure file shares.
76
+
- Only available for SSD (premium) Azure file shares. Not available for HDD (standard) Azure file shares.
70
77
- Only supported on clients that are using SMB 3.1.1. Ensure SMB client operating systems are patched to recommended levels.
71
78
- Maximum number of channels is four, for details see [here](/troubleshoot/azure/azure-storage/files-troubleshoot-performance?toc=/azure/storage/files/toc.json#cause-4-number-of-smb-channels-exceeds-four).
72
79
@@ -88,7 +95,7 @@ In most scenarios, particularly multi-threaded workloads, clients should see imp
88
95
89
96
### Verify SMB Multichannel is configured correctly
90
97
91
-
1. Create a new premium file share or use an existing premium share.
98
+
1. Create a new SSD (premium) file share or use an existing SSD (premium) share.
92
99
1. Ensure your client supports SMB Multichannel (one or more network adapters has receive-side scaling enabled). Refer to the [Windows documentation](/azure-stack/hci/manage/manage-smb-multichannel) for more details.
93
100
1. Mount a file share to your client.
94
101
1. Generate load with your application.
@@ -104,7 +111,7 @@ There are two categories of read/write workload patterns: single-threaded and mu
104
111
-**Multi-threaded/multiple files**:
105
112
Depending on the workload pattern, you should see significant performance improvement in read and write I/Os over multiple channels. The performance gains vary from anywhere between 2x to 4x in terms of IOPS, throughput, and latency. For this category, SMB Multichannel should be enabled for the best performance.
106
113
-**Multi-threaded/single file**:
107
-
For most use cases in this category, workloads will benefit from having SMB Multichannel enabled, especially if the workload has an average I/O size > ~16k. A few example scenarios that benefit from SMB Multichannel are backup or recovery of a single large file. An exception where you might want to disable SMB Multichannel is if your workload is heavy on small I/Os. In that case, you might observe a slight performance loss of ~10%. Depending on the use case, consider spreading load across multiple files, or disable the feature. See the [Configuration](#configuration) section for details.
114
+
For most use cases in this category, workloads benefit from having SMB Multichannel enabled, especially if the workload has an average I/O size > ~16k. A few example scenarios that benefit from SMB Multichannel are backup or recovery of a single large file. An exception where you might want to disable SMB Multichannel is if your workload is heavy on small I/Os. In that case, you might observe a slight performance loss of ~10%. Depending on the use case, consider spreading load across multiple files, or disable the feature. See the [Configuration](#configuration) section for details.
108
115
-**Single-threaded/multiple files or single file**:
109
116
For most single-threaded workloads, there are minimum performance benefits due to lack of parallelism. Usually there is a slight performance degradation of ~10% if SMB Multichannel is enabled. In this case, it's ideal to disable SMB Multichannel, with one exception. If the single-threaded workload can distribute load across multiple files and uses on an average larger I/O size (> ~16k), then there should be slight performance benefits from SMB Multichannel.
110
117
@@ -147,20 +154,20 @@ The load was generated against a single 128 GiB file. With SMB Multichannel enab
147
154
148
155
## Metadata caching for premium SMB file shares
149
156
150
-
Metadata caching is an enhancement for premium SMB Azure file shares aimed to improve the following:
157
+
Metadata caching is an enhancement for SSD (premium) SMB Azure file shares aimed to improve the following:
151
158
152
159
- Reduce metadata latency
153
160
- Raised metadata scale limits
154
161
- Increase latency consistency, available IOPS, and boost network throughput
155
162
156
-
This preview feature improves the following metadata APIs and can be used from both Windows and Linux clients:
163
+
This feature improves the following metadata APIs and can be used from both Windows and Linux clients:
157
164
158
165
- Create
159
166
- Open
160
167
- Close
161
168
- Delete
162
169
163
-
Currently this preview feature is only available for premium SMB file shares (file shares in the FileStorage storage account kind). There are no additional costs associated with using this feature.
170
+
Currently this feature is only available for SSD (premium) SMB file shares (file shares in the FileStorage storage account kind). There are no extra costs associated with using this feature.
164
171
165
172
### Register for the feature
166
173
@@ -171,7 +178,7 @@ To get started, register for the feature using the Azure portal or Azure PowerSh
171
178
1. Sign in to the [Azure portal](https://portal.azure.com?azure-portal=true).
172
179
2. Search for and select **Preview features**.
173
180
3. Select the **Type** filter and select **Microsoft.Storage**.
174
-
4. Select **Azure Premium Files Metadata Cache Preview** and then select **Register**.
181
+
4. Select **Azure Premium Files Metadata Cache** and then select **Register**.
![prmerger-automator[bot]](https://avatars.githubusercontent.com/u/22479449?v=4&size=40){kind=avatar}
0 commit comments