Skip to content

Commit 58c1c8c

Browse files
committed
Updating size
1 parent c806d47 commit 58c1c8c

File tree

1 file changed

+7
-7
lines changed

1 file changed

+7
-7
lines changed

articles/storage/files/storage-sync-files-planning.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ description: Learn what to consider when planning for an Azure Files deployment.
44
author: roygara
55
ms.service: storage
66
ms.topic: conceptual
7-
ms.date: 12/18/2019
7+
ms.date: 01/15/2020
88
ms.author: rogarana
99
ms.subservice: files
1010
---
@@ -342,13 +342,13 @@ In the following table, we have provided both the size of the namespace as well
342342
| Namespace size - files & directories (millions) | Typical capacity (TiB) | CPU Cores | Recommended memory (GiB) |
343343
|---------|---------|---------|---------|
344344
| 3 | 1.4 | 2 | 8 (initial sync)/ 2 (typical churn) |
345-
| 5 | 2.3 | 2 | 16 (initial sync)/ 4 (typical churn) |
346-
| 10 | 4.7 | 4 | 32 (initial sync)/ 8 (typical churn) |
347-
| 30 | 14.0 | 8 | 48 (initial sync)/ 16 (typical churn) |
348-
| 50 | 23.3 | 16 | 64 (initial sync)/ 32 (typical churn) |
349-
| 100* | 46.6 | 32 | 128 (initial sync)/ 32 (typical churn) |
345+
| 5 | 2.4 | 2 | 16 (initial sync)/ 4 (typical churn) |
346+
| 10 | 4.8 | 4 | 32 (initial sync)/ 8 (typical churn) |
347+
| 30 | 14.3 | 8 | 48 (initial sync)/ 16 (typical churn) |
348+
| 50 | 23.8 | 16 | 64 (initial sync)/ 32 (typical churn) |
349+
| 100* | 47.7 | 32 | 128 (initial sync)/ 32 (typical churn) |
350350

351-
\*More than 100 million files & directories is not supported at this time. This is a soft limit.
351+
\*More than 100 million files & directories has not been tested. This is a soft limit.
352352

353353
> [!TIP]
354354
> Initial synchronization of a namespace is an intensive operation and we recommend allocating more memory until initial synchronization is complete. This isn't required but, may speed up initial sync.

0 commit comments

Comments
 (0)