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/analyze-files-metrics.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -348,7 +348,7 @@ The following chart illustrates a workload that experienced a sudden increase in
348
348
349
349
If your workload encounters **Success with Metadata Warnings** or **Success with Metadata Throttling** response types, consider implementing one or more of the following recommendations:
350
350
351
-
- For SSD SMB file shares, enable [Metadata Caching](smb-performance.md#metadata-caching-for-premium-smb-file-shares).
351
+
- For SSD SMB file shares, enable [Metadata Caching](smb-performance.md#metadata-caching-for-ssd-file-shares).
352
352
- Distribute (shard) your workload across multiple file shares.
Copy file name to clipboardExpand all lines: articles/storage/files/files-whats-new.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -82,7 +82,7 @@ HDD file shares that are Geo (GRS) or GeoZone (GZRS) redundant can now scale up
82
82
83
83
#### Metadata caching for SSD SMB file shares is in public preview
84
84
85
-
Metadata caching is an enhancement for SMB Azure SSD file shares aimed to reduce metadata latency, increase available IOPS, and boost network throughput. [Learn more](smb-performance.md#metadata-caching-for-premium-smb-file-shares).
85
+
Metadata caching is an enhancement for SMB Azure SSD file shares aimed to reduce metadata latency, increase available IOPS, and boost network throughput. [Learn more](smb-performance.md#metadata-caching-for-ssd-file-shares).
86
86
87
87
#### Snapshot support for NFS file shares is generally available
@@ -35,8 +35,8 @@ The following tips might help you optimize performance:
35
35
- Ensure that your storage account and your client are co-located in the same Azure region to reduce network latency.
36
36
- Use multi-threaded applications and spread load across multiple files.
37
37
- Performance benefits of SMB Multichannel increase with the number of files distributing load.
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.
38
+
- SSD share performance is bound by provisioned share size, including IOPS and throughput and single file limits. For details, see [understanding the provisioning v1 model](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 approximately 1.86 GiB / sec, 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.
40
40
- The initial test is usually a warm-up. Discard the results and repeat the test.
41
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.
42
42
@@ -48,7 +48,7 @@ Higher I/O sizes drive higher throughput and will have higher latencies, resulti
48
48
49
49
## SMB Multichannel
50
50
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.
51
+
SMB Multichannel enables an SMB client to establish multiple network connections to an SMB file share. Azure Files supports SMB Multichannel on SSD 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.
52
52
53
53
### Benefits
54
54
@@ -63,7 +63,7 @@ SMB Multichannel enables clients to use multiple network connections that provid
63
63
-**Automatic configuration**:
64
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.
65
65
-**Cost optimization**:
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.
66
+
Workloads can achieve higher scale from a single VM, or a small set of VMs, while connecting to SSD file shares. This could reduce the total cost of ownership by reducing the number of VMs necessary to run and manage a workload.
67
67
68
68
To learn more about SMB Multichannel, refer to the [Windows documentation](/azure-stack/hci/manage/manage-smb-multichannel).
69
69
@@ -73,7 +73,7 @@ This feature provides greater performance benefits to multi-threaded application
73
73
74
74
SMB Multichannel for Azure file shares currently has the following restrictions:
75
75
76
-
- Only available for SSD (premium) Azure file shares. Not available for HDD (standard) Azure file shares.
76
+
- Only available for SSD file shares. Not available for HDD Azure file shares.
77
77
- Only supported on clients that are using SMB 3.1.1. Ensure SMB client operating systems are patched to recommended levels.
78
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).
79
79
@@ -95,7 +95,7 @@ In most scenarios, particularly multi-threaded workloads, clients should see imp
95
95
96
96
### Verify SMB Multichannel is configured correctly
97
97
98
-
1. Create a new SSD (premium) file share or use an existing SSD (premium) share.
98
+
1. Create a new SSD file share or use an existing SSD file share.
99
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.
100
100
1. Mount a file share to your client.
101
101
1. Generate load with your application.
@@ -119,10 +119,6 @@ There are two categories of read/write workload patterns: single-threaded and mu
119
119
120
120
For the charts in this article, the following configuration was used: A single Standard D32s v3 VM with a single RSS enabled NIC with four channels. Load was generated using diskspd.exe, multiple-threaded with IO depth of 10, and random I/Os with various I/O sizes.
121
121
122
-
| Size | vCPU | Memory: GiB | Temp storage (SSD) GiB | Max data disks | Max cached and temp storage throughput: IOPS/MBps (cache size in GiB) | Max uncached disk throughput: IOPS/MBps | Max NICs|Expected network bandwidth (Mbps) |
### Multi-threaded/multiple files with SMB Multichannel
127
123
128
124
Load was generated against 10 files with various IO sizes. The scale up test results showed significant improvements in both IOPS and throughput test results with SMB Multichannel enabled. The following diagrams depict the results:
@@ -133,7 +129,7 @@ Load was generated against 10 files with various IO sizes. The scale up test res
133
129
134
130
- On a single NIC, for reads, performance increase of 2x-3x was observed and for writes, gains of 3x-4x in terms of both IOPS and throughput.
135
131
- SMB Multichannel allowed IOPS and throughput to reach VM limits even with a single NIC and the four channel limit.
136
-
- Since egress (or reads to storage) is not metered, read throughput was able to exceed the VM published limit of 16,000 Mbps (2 GiB/s). The test achieved >2.7 GiB/s. Ingress (or writes to storage) are still subject to VM limits.
132
+
- Since egress (or reads to storage) is not metered, read throughput was able to exceed the VM published limit of approximately 1.86 GiB / sec. The test achieved >2.7 GiB / sec. Ingress (or writes to storage) are still subject to VM limits.
137
133
- Spreading load over multiple files allowed for substantial improvements.
138
134
139
135
An example command used in this testing is:
@@ -152,9 +148,9 @@ The load was generated against a single 128 GiB file. With SMB Multichannel enab
152
148
- For smaller I/O sizes, there was a slight impact of ~10% on performance with SMB Multichannel enabled. This could be mitigated by spreading the load over multiple files, or disabling the feature.
153
149
- Performance is still bound by [single file limits](storage-files-scale-targets.md#file-scale-targets).
154
150
155
-
## Metadata caching for premium SMB file shares
151
+
## Metadata caching for SSD file shares
156
152
157
-
Metadata caching is an enhancement for SSD (premium) SMB Azure file shares aimed to improve the following:
153
+
Metadata caching is an enhancement for SSD Azure file shares aimed to improve the following:
158
154
159
155
- Reduce metadata latency
160
156
- Raised metadata scale limits
@@ -167,7 +163,7 @@ This feature improves the following metadata APIs and can be used from both Wind
167
163
- Close
168
164
- Delete
169
165
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.
166
+
Currently this feature is only available for SSD file shares. There are no extra costs associated with using this feature.
![prmerger-automator[bot]](https://avatars.githubusercontent.com/u/22479449?v=4&size=40){kind=avatar}
0 commit comments