Skip to content

Commit 9f8110e

Browse files
authored
Update storage-files-scale-targets.md
1 parent aa1572c commit 9f8110e

File tree

1 file changed

+4
-2
lines changed

1 file changed

+4
-2
lines changed

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

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -129,6 +129,8 @@ To help you plan your deployment for each of the stages, below are the results o
129129
| Network | 1 Gbps Network |
130130
| Workload | General Purpose File Server|
131131

132+
### Initial one-time provisioning
133+
132134
| Initial one-time provisioning | Details |
133135
|-|-|
134136
| Number of objects | 25 million objects |
@@ -138,8 +140,6 @@ To help you plan your deployment for each of the stages, below are the results o
138140
| Upload Throughput | 20 objects per second per sync group |
139141
| Namespace Download Throughput | 400 objects per second |
140142

141-
### Initial one-time provisioning
142-
143143
**Initial cloud change enumeration**: When a new sync group is created, initial cloud change enumeration is the first step that will execute. In this process, the system will enumerate all the items in the Azure File Share. During this process, there will be no sync activity i.e. no items will be downloaded from cloud endpoint to server endpoint and no items will be uploaded from server endpoint to cloud endpoint. Sync activity will resume once initial cloud change enumeration completes.
144144
The rate of performance is 80 objects per second. Customers can estimate the time it will take to complete initial cloud change enumeration by determining the number of items in the cloud share and using the following formulae to get the time in days.
145145

@@ -157,6 +157,8 @@ Splitting your data into multiple server endpoints and sync groups can speed up
157157

158158
**Namespace download throughput** When a new server endpoint is added to an existing sync group, the Azure File Sync agent does not download any of the file content from the cloud endpoint. It first syncs the full namespace and then triggers background recall to download the files, either in their entirety or, if cloud tiering is enabled, to the cloud tiering policy set on the server endpoint.
159159

160+
### Ongoing sync
161+
160162
| Ongoing sync | Details |
161163
|-|--|
162164
| Number of objects synced| 125,000 objects (~1% churn) |

0 commit comments

Comments
 (0)