Lack of clarity on scaling target and large file share / quota interactions

[erishiamu]

You specify in subscript 2 under 'Azure file share scale targets' that in order for the large file share change to impact scale targets the quota needs to be increased. Does this behave like premium shares where the allocated quota impacts the IOPS and request throttling limits, or is any increase above 5tb enough to enable the higher threshholds for the file share? Clarification here is needed in order for admins to make informed decisions about sharing sizing and quota allocation for production workloads.

---

Document Details

⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

• ID: 991338c0-1a61-99e1-41ea-45fd5d5fd63d
• Version Independent ID: f2dd8b70-29f2-bb22-38f5-097c5eb6b797
• Content: Azure Files scalability and performance targets
• Content Source: articles/storage/files/storage-files-scale-targets.md
• Service: storage
• Sub-service: files
• GitHub Login: @khdownie
• Microsoft Alias: kendownie

[Naveenommi-MSFT]

@erishiamu Thanks for your feedback! We will investigate and update as appropriate.

[ManoharLakkoju-MSFT]

@erishiamu Updated article to clarify Azure Files supports more than 2,000 open handles per share. However, if an application keeps an open handle on the root of the share, the share root limit will be reached before the per file or directory limit is reached.

If there are any further questions regarding the documentation, please tag me in your reply and we will be happy to continue the conversation.

[khdownie]

@ManoharLakkoju-MSFT the response above has nothing to do with the user's question.

[khdownie]

@erishiamu very soon we are going to deploy a fix to no longer requiring increasing the share quota. But for now you have to do two things:

• Enable the Large file shares setting on the storage account. • Increase the quota so that it is larger than 5TiB. Once you increase the share beyond 5TiB, the share will be split across multiple storage nodes (partitions).

https://learn.microsoft.com/en-us/azure/storage/files/storage-how-to-create-file-share?tabs=azure-portal#enable-large-files-shares-on-an-existing-account

[erishiamu]

@ManoharLakkoju-MSFT That isn't related to my question. For paygo/std accounts IOPS and throughput throttling is not based on quota. I'm trying to confirm if that is true when large file shares are enabled, or if they behave like premium shares and scale based on the set quota.

For ex, the left column indicates the IOPS limit is 20k but the throughput limit is up to 300Mib/s.

@khdownie Thanks! I'm less concerned about needing to increase the quota and more concerned about how much. So can I infer from this that any increase in quota (and soon, simply enabling large file shares) will take the IOPS and throttling to the LFS max?

[ManoharLakkoju-MSFT]

@khdownie Can you please check and add your comments on this doc update request as applicable.

[khdownie]

@erishiamu we recommend that you set it to 100TiB since you pay for what you use (not the provisioned size). However, any size beyond 5TiB will do.

[erishiamu]

Fabulous thank you for clarifying and advising on the upcoming change @khdownie.