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/storage-files-scale-targets.md
+87-62Lines changed: 87 additions & 62 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,90 +9,115 @@ ms.author: kendownie
9
9
---
10
10
11
11
# Scalability and performance targets for Azure Files and Azure File Sync
12
-
13
12
[Azure Files](storage-files-introduction.md) offers fully managed file shares in the cloud that are accessible via the Server Message Block (SMB) and Network File System (NFS) file system protocols. This article discusses the scalability and performance targets for Azure storage accounts, Azure Files, and Azure File Sync.
14
13
15
14
The targets listed here might be affected by other variables in your deployment. For example, the performance of I/O for a file might be impacted by your SMB client's behavior and by your available network bandwidth. You should test your usage pattern to determine whether the scalability and performance of Azure Files meet your requirements.
16
15
17
16
## Applies to
18
-
19
-
| File share type | SMB | NFS |
20
-
|-|:-:|:-:|
21
-
| Standard file shares (GPv2), LRS/ZRS |||
22
-
| Standard file shares (GPv2), GRS/GZRS |||
Azure file shares are deployed into storage accounts, which are top-level objects that represent a shared pool of storage. This pool of storage can be used to deploy multiple file shares. There are therefore three categories to consider: storage accounts, Azure file shares, and individual files.
28
32
29
33
### Storage account scale targets
30
-
31
34
Storage account scale targets apply at the storage account level. There are two main types of storage accounts for Azure Files:
32
35
33
-
-**General purpose version 2 (GPv2) storage accounts**: GPv2 storage accounts allow you to deploy Azure file shares on standard/hard disk-based (HDD-based) hardware. In addition to storing Azure file shares, GPv2 storage accounts can store other storage resources such as blob containers, queues, or tables. File shares can be deployed into the transaction optimized (default), hot, or cool tiers.
34
-
35
-
-**FileStorage storage accounts**: FileStorage storage accounts allow you to deploy Azure file shares on premium/solid-state disk-based (SSD-based) hardware. FileStorage accounts can only be used to store Azure file shares; no other storage resources (blob containers, queues, tables, etc.) can be deployed in a FileStorage account.
| Maximum number of file shares | Unlimited | Unlimited, total provisioned size of all shares must be less than max than the max storage account capacity |
| Throughput (ingress + egress) for ZRS<br /><ul><li>Australia East</li><li>Central US</li><li>East US</li><li>East US 2</li><li>Japan East</li><li>North Europe</li><li>South Central US</li><li>Southeast Asia</li><li>UK South</li><li>West Europe</li><li>West US 2</li></ul> | <ul><li>Ingress: 7,152 MiB/sec</li><li>Egress: 14,305 MiB/sec</li></ul> | 10,340 MiB/sec |
45
-
| Throughput (ingress + egress) for redundancy/region combinations not listed in the previous row | <ul><li>Ingress: 2,980 MiB/sec</li><li>Egress: 5,960 MiB/sec</li></ul> | 10,340 MiB/sec |
46
-
| Maximum number of virtual network rules | 200 | 200 |
47
-
| Maximum number of IP address rules | 200 | 200 |
48
-
| Management read operations | 800 per 5 minutes | 800 per 5 minutes |
49
-
| Management write operations | 10 per second/1200 per hour | 10 per second/1200 per hour |
50
-
| Management list operations | 100 per 5 minutes | 100 per 5 minutes |
51
-
52
-
<sup>1</sup> With a quota increase, you can create up to 500 storage accounts with standard endpoints per region. For more information, see [Increase Azure Storage account quotas](/azure/quotas/storage-account-quota-requests).
53
-
<sup>2</sup> General-purpose version 2 storage accounts support higher capacity limits and higher limits for ingress by request. To request an increase in account limits, contact [Azure Support](https://azure.microsoft.com/support/faq/).
36
+
-**FileStorage storage accounts**: FileStorage storage accounts allow you to deploy Azure file shares with a provisioned billing model. FileStorage accounts can only be used to store Azure file shares; no other storage resources (blob containers, queues, tables, etc.) can be deployed in a FileStorage account.
37
+
38
+
-**General purpose version 2 (GPv2) storage accounts**: GPv2 storage accounts allow you to deploy pay-as-you-go file shares on HDD-based hardware. In addition to storing Azure file shares, GPv2 storage accounts can store other storage resources such as blob containers, queues, or tables.
|Minimum size of a file share | No minimum|100 GiB (provisioned)|
62
-
|Provisioned size increase/decrease unit | N/A | 1 GiB|
63
-
|Maximum size of a file share | 100 TiB | 100 TiB|
64
-
|Maximum number of files in a file share | No limit | No limit|
65
-
| Maximum request rate (Max IOPS) | 20,000 | <ul><li>Baseline IOPS: 3000 + 1 IOPS per GiB, up to 102,400</li><li>IOPS bursting: Max (10,000, 3x IOPS per GiB), up to 102,400</li></ul>|
66
-
|Throughput (ingress + egress) for a single file share (MiB/sec) | Up to storage account limits | 100 + CEILING(0.04 * ProvisionedStorageGiB) + CEILING(0.06 * ProvisionedStorageGiB)|
67
-
| Maximum number of share snapshots | 200 snapshots | 200 snapshots|
68
-
| Maximum object name length<sup>3</sup> (full pathname including all directories, file names, and backslash characters) |2,048 characters | 2,048 characters|
69
-
| Maximum length of individual pathname component<sup>2</sup> (in the path \A\B\C\D, each letter represents a directory or file that is an individual component) | 255 characters|255 characters|
70
-
|Hard link limit (NFS only) |N/A | 178|
71
-
| Maximum number of SMB Multichannel channels | N/A | 4|
72
-
|Maximum number of stored access policies per file share | 5|5|
73
-
74
-
<sup>1</sup> The limits for standard file shares apply to all three of the tiers available for standard file shares: transaction optimized, hot, and cool.
75
-
76
-
<sup>2</sup> Azure Files enforces certain [naming rules](/rest/api/storageservices/naming-and-referencing-shares--directories--files--and-metadata#directory-and-file-names) for directory and file names.
|Maximum number of files | Unlimited | Unlimited | Unlimited|
100
+
| Maximum IOPS | 102,400 IOPS (dependent on provisioning) | 50,000 IOPS (dependent on provisioning) | 20,000 IOPS|
101
+
| Maximum throughput | 10,340 MiB / sec (dependent on provisioning) | 5,120 IOPS (dependent on provisioning) |Up to storage account limits|
102
+
| Maximum number of share snapshots | 200 snapshots | 200 snapshots|200 snapshots|
103
+
|Maximum filename length<sup>3</sup> (full pathname including all directories, file names, and backslash characters) |2,048 characters | 2,048 characters | 2,048 characters|
104
+
| Maximum length of individual pathname component<sup>2</sup> (in the path \A\B\C\D, each letter represents a directory or file that is an individual component) | 255 characters | 255 characters | 255 characters|
105
+
|Hard link limit (NFS only) | 178 | N/A|N/A|
106
+
| Maximum number of SMB Multichannel channels | 4 | N/A | N/A |
107
+
| Maximum number of stored access policies per file share | 5 | 5 | 5 |
108
+
109
+
<sup>3</sup> Azure Files enforces certain [naming rules](/rest/api/storageservices/naming-and-referencing-shares--directories--files--and-metadata#directory-and-file-names) for directory and file names.
77
110
78
111
### File scale targets
79
-
80
112
File scale targets apply to individual files stored in Azure file shares.
81
113
82
-
| Attribute |Files in standard file shares | Files in premium file shares |
| Maximum concurrent request rate | 1,000 IOPS | Up to 8,000<sup>1</sup> |
86
-
| Maximum ingress for a file | 60 MiB/sec | 200 MiB/sec (Up to 1 GiB/s with SMB Multichannel)<sup>2</sup> |
87
-
| Maximum egress for a file | 60 MiB/sec | 300 MiB/sec (Up to 1 GiB/s with SMB Multichannel)<sup>2</sup> |
88
-
| Maximum concurrent handles for root directory<sup>3</sup> | 10,000 handles | 10,000 handles |
89
-
| Maximum concurrent handles per file and directory<sup>3</sup> | 2,000 handles | 2,000 handles |
90
-
91
-
<sup>1 Applies to read and write I/Os (typically smaller I/O sizes less than or equal to 64 KiB). Metadata operations, other than reads and writes, may be lower. These are soft limits, and throttling can occur beyond these limits.</sup>
92
-
93
-
<sup>2 Subject to machine network limits, available bandwidth, I/O sizes, queue depth, and other factors. For details see [SMB Multichannel performance](./smb-performance.md).</sup>
94
-
95
-
<sup>3 Azure Files supports 10,000 open handles on the root directory and 2,000 open handles per file and directory within the share. The number of active users supported per share is dependent on the applications that are accessing the share. If your applications aren't opening a handle on the root directory, Azure Files can support more than 10,000 active users per share. However, if you're using Azure Files to store disk images for large-scale virtual desktop workloads, you might run out of handles for the root directory or per file/directory. In this case, you might need to use multiple Azure file shares. For more information, see [Azure Files sizing guidance for Azure Virtual Desktop](#azure-files-sizing-guidance-for-azure-virtual-desktop).</sup>
116
+
| Maximum file size | 4 TiB | 4 TiB | 4 TiB |
117
+
| Maximum data IOPS per file | 8,000 IOPS | 1,000 IOPS | 1,000 IOPS |
0 commit comments