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
description: Troubleshoot performance issues with Azure file shares and discover potential causes and associated workarounds for these problems.
4
4
ms.service: azure-file-storage
5
5
ms.custom: sap:Performance, linux-related-content
6
-
ms.date: 05/21/2024
6
+
ms.date: 01/23/2025
7
7
ms.reviewer: kendownie, v-weizhu
8
8
#Customer intent: As a system admin, I want to troubleshoot performance issues with Azure file shares to improve performance for applications and users.
9
9
---
@@ -265,11 +265,9 @@ Lack of support for directory leases.
265
265
266
266
## Slow enumeration of files and folders
267
267
268
-
### Cause
269
-
270
-
This problem can occur if there isn't enough cache on the client machine for large directories.
268
+
This problem can occur if there isn't enough cache or memory on the client machine for large directories.
271
269
272
-
### Solution
270
+
##[Windows](#tab/windows)
273
271
274
272
To resolve this problem, adjust the `DirectoryCacheEntrySizeMax` registry value to allow caching of larger directory listings in the client machine:
275
273
@@ -279,6 +277,12 @@ To resolve this problem, adjust the `DirectoryCacheEntrySizeMax` registry value
279
277
280
278
For example, you can set it to `0x100000` and see if performance improves.
281
279
280
+
## [Linux](#tab/linux)
281
+
282
+
The amount of memory available influences the number of inode hash buckets the system has, which impacts/improves enumeration performance for large directories. You can modify the number of hash buckets the system has to reduce the hash collisions that can occur during large enumeration workloads. For instructions, see [Increase the number of hash buckets](/azure/storage/files/nfs-large-directories#increase-the-number-of-hash-buckets).
283
+
284
+
---
285
+
282
286
## Slow file copying to and from Azure file shares
283
287
284
288
You might see slow performance when you try to transfer files to the Azure Files service. If you don't have a specific minimum I/O size requirement, we recommend that you use 1 MiB as the I/O size for optimal performance.
0 commit comments