Skip to content

Commit 1a21c2f

Browse files
committed
incorporate handle limits preview
1 parent b84c886 commit 1a21c2f

File tree

3 files changed

+47
-12
lines changed

3 files changed

+47
-12
lines changed

articles/storage/files/smb-performance.md

Lines changed: 26 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ description: Learn about ways to improve performance and throughput for SSD (pre
44
author: khdownie
55
ms.service: azure-file-storage
66
ms.topic: concept-article
7-
ms.date: 01/22/2025
7+
ms.date: 05/29/2025
88
ms.author: kendownie
99
ms.custom: references_regions
1010
---
@@ -163,9 +163,9 @@ This feature improves the following metadata APIs and can be used from both Wind
163163
- Close
164164
- Delete
165165

166-
Currently this feature is only available for SSD file shares. 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. You can also register to increase file handle limits for SSD file shares (preview).
167167

168-
### Register for the feature
168+
### Register for the metadata caching feature
169169

170170
To get started, register for the feature using the Azure portal or Azure PowerShell.
171171

@@ -186,11 +186,32 @@ Register-AzProviderFeature -FeatureName AzurePremiumFilesMetadataCacheFeature -P
186186
```
187187
---
188188

189+
### Register for increased file handle limits (preview)
190+
191+
To increase the maximum number of concurrent handles per file and directory for SSD SMB file shares from 2,000 to 10,000, register for the preview feature using the Azure portal or Azure PowerShell. If you have questions, email [email protected].
192+
193+
# [Azure portal](#tab/portal)
194+
195+
1. Sign in to the [Azure portal](https://portal.azure.com?azure-portal=true).
196+
2. Search for and select **Preview features**.
197+
3. Select the **Type** filter and select **Microsoft.Storage**.
198+
4. Select **Azure Premium Files Increased Maximum Opened Handles Count** and then select **Register**.
199+
200+
# [Azure PowerShell](#tab/powershell)
201+
202+
To register your subscription using Azure PowerShell, run the following commands. Replace `<your-subscription-id>` and `<your-tenant-id>` with your own values.
203+
204+
```azurepowershell-interactive
205+
Connect-AzAccount -SubscriptionId <your-subscription-id> -TenantId <your-tenant-id>
206+
Register-AzProviderFeature -FeatureName HigherHandlesCountOnSmb -ProviderNamespace Microsoft.Storage
207+
```
208+
---
209+
189210
> [!IMPORTANT]
190211
> - Although listed under Preview Features, we honor GA SLAs and will soon make this the default for all accounts, removing the need for registration.
191-
> - Allow 1-2 days for accounts to be onboarded once registration is complete.
212+
> - Allow 2-6 hours for accounts to be onboarded once registration is complete.
192213
193-
### Regional availability
214+
### Regional availability for metadata caching
194215

195216
Supported regions:
196217

articles/storage/files/storage-files-scale-targets.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -121,7 +121,9 @@ File scale targets apply to individual files stored in Azure file shares.
121121
| Maximum data IOPS per file | 8,000 IOPS | 1,000 IOPS | 1,000 IOPS |
122122
| Maximum throughput per file | 1,024 MiB / sec | 60 MiB / sec | 60 MiB / sec |
123123
| Maximum concurrent handles for root directory | 10,000 handles | 10,000 handles | 10,000 handles |
124-
| Maximum concurrent handles per file and directory | 2,000 handles | 2,000 handles | 2,000 handles |
124+
| Maximum concurrent handles per file and directory | 2,000 handles\* | 2,000 handles | 2,000 handles |
125+
126+
\* The maximum number of concurrent handles per file and directory is a soft limit for SSD SMB file shares. If you need to scale beyond this limit, you can [enable metadata caching](smb-performance.md#register-for-the-metadata-caching-feature), and register for [increased file handle limits (preview)](smb-performance.md#register-for-increased-file-handle-limits-preview).
125127

126128
### Azure Files sizing guidance for Azure Virtual Desktop
127129

articles/storage/files/virtual-desktop-workloads.md

Lines changed: 18 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -14,11 +14,18 @@ Azure Files is the recommended file storage solution for a virtual desktop envir
1414

1515
## Applies to
1616

17-
| File share type | SMB | NFS |
18-
|-|:-:|:-:|
19-
| Standard file shares (GPv2), LRS/ZRS | ![Yes](../media/icons/yes-icon.png) | ![No](../media/icons/no-icon.png) |
20-
| Standard file shares (GPv2), GRS/GZRS | ![Yes](../media/icons/yes-icon.png) | ![No](../media/icons/no-icon.png) |
21-
| Premium file shares (FileStorage), LRS/ZRS | ![Yes](../media/icons/yes-icon.png) | ![No](../media/icons/no-icon.png) |
17+
| Management model | Billing model | Media tier | Redundancy | SMB | NFS |
18+
|-|-|-|-|:-:|:-:|
19+
| Microsoft.Storage | Provisioned v2 | HDD (standard) | Local (LRS) | ![Yes](../media/icons/yes-icon.png) | ![No](../media/icons/no-icon.png) |
20+
| Microsoft.Storage | Provisioned v2 | HDD (standard) | Zone (ZRS) | ![Yes](../media/icons/yes-icon.png) | ![No](../media/icons/no-icon.png) |
21+
| Microsoft.Storage | Provisioned v2 | HDD (standard) | Geo (GRS) | ![Yes](../media/icons/yes-icon.png) | ![No](../media/icons/no-icon.png) |
22+
| Microsoft.Storage | Provisioned v2 | HDD (standard) | GeoZone (GZRS) | ![Yes](../media/icons/yes-icon.png) | ![No](../media/icons/no-icon.png) |
23+
| Microsoft.Storage | Provisioned v1 | SSD (premium) | Local (LRS) | ![Yes](../media/icons/yes-icon.png) | ![No](../media/icons/no-icon.png) |
24+
| Microsoft.Storage | Provisioned v1 | SSD (premium) | Zone (ZRS) | ![Yes](../media/icons/yes-icon.png) | ![No](../media/icons/no-icon.png) |
25+
| Microsoft.Storage | Pay-as-you-go | HDD (standard) | Local (LRS) | ![Yes](../media/icons/yes-icon.png) | ![No](../media/icons/no-icon.png) |
26+
| Microsoft.Storage | Pay-as-you-go | HDD (standard) | Zone (ZRS) | ![Yes](../media/icons/yes-icon.png) | ![No](../media/icons/no-icon.png) |
27+
| Microsoft.Storage | Pay-as-you-go | HDD (standard) | Geo (GRS) | ![Yes](../media/icons/yes-icon.png) | ![No](../media/icons/no-icon.png) |
28+
| Microsoft.Storage | Pay-as-you-go | HDD (standard) | GeoZone (GZRS) | ![Yes](../media/icons/yes-icon.png) | ![No](../media/icons/no-icon.png) |
2229

2330
## Prerequisites
2431

@@ -41,6 +48,8 @@ Azure Files offers different billing models, including provisioned and pay-as-yo
4148

4249
While Azure Files can support thousands of concurrent virtual desktop users from a single file share, it's critical to properly test your workloads against the size and type of file share you're using. Your requirements might vary based on number of users and profile size.
4350

51+
Virtual desktops with home directories or other workloads that are primarily interacting with many small files, directories, or handles can benefit from [metadata caching](smb-performance.md#metadata-caching-for-ssd-file-shares) on SSD file shares.
52+
4453
The following table lists our general recommendations based on the number of concurrent users. This table is based on the assumption that the user profile has a capacity of 5 GiB and a performance of 50 IOPS during sign in and 20 IOPS during steady state.
4554

4655
| **Number of virtual desktop users** | **Recommended file storage** |
@@ -52,7 +61,10 @@ The following table lists our general recommendations based on the number of con
5261

5362
## Azure Files sizing guidance for Azure Virtual Desktop
5463

55-
In large scale Azure Virtual Desktop deployments, you might run out of handles if you're using a single Azure file share. This section describes how various types of disk images consume handles and provides sizing guidance based on the technology you're using.
64+
In large-scale VDI environments, tens of thousands of users may need to access the same file simultaneously, especially during application launches and session setups. In these situations, you might run out of handles, especially if you're using a single Azure file share. This section describes how various types of disk images consume handles and provides sizing guidance based on the technology you're using.
65+
66+
> [!TIP]
67+
> Historically, Azure Files had a 2,000 concurrent handle limit per file and directory. If you need to scale beyond this limit, you can use SSD file shares, [enable metadata caching](smb-performance.md#register-for-the-metadata-caching-feature), and register for [increased file handle limits (preview)](smb-performance.md#register-for-increased-file-handle-limits-preview).
5668
5769
### FSLogix
5870

0 commit comments

Comments
 (0)