Skip to content

Commit 1da859c

Browse files
authored
Update storage-files-scale-targets.md
1 parent 17a646e commit 1da859c

File tree

1 file changed

+3
-2
lines changed

1 file changed

+3
-2
lines changed

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

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -109,7 +109,7 @@ The following table indicates which target are soft, representing the Microsoft
109109
> [!Note]
110110
> An Azure File Sync endpoint can scale up to the size of an Azure file share. If the Azure file share size limit is reached, sync will not be able to operate.
111111
112-
### Azure File Sync performance metrics
112+
## Azure File Sync performance metrics
113113
Since the Azure File Sync agent runs on a Windows Server machine that connects to the Azure file shares, the effective sync performance depends upon a number of factors in your infrastructure: Windows Server and the underlying disk configuration, network bandwidth between the server and the Azure storage, file size, total dataset size, and the activity on the dataset. Since Azure File Sync works on the file level, the performance characteristics of an Azure File Sync-based solution should be measured by the number of objects (files and directories) processed per second.
114114

115115
For Azure File Sync, performance is critical in two stages:
@@ -119,7 +119,8 @@ For Azure File Sync, performance is critical in two stages:
119119
> [!Note]
120120
> When many server endpoints in the same sync group are syncing at the same time, they are contending for cloud service resources. As a result, upload performance will be impacted. In extreme cases, some sync sessions will fail to access the resources, and will fail. However, those sync sessions will resume shortly and eventually succeed once the congestion is reduced.
121121
122-
To help you plan your deployment for each of the stages, below are the results observed during the internal testing on a system with a config
122+
## Internal test results
123+
To help you plan your deployment for each of the stages (initial one-time provisioning and ongoing sync), below are the results observed during the internal testing on a system with the following configuration:
123124

124125
| System configuration | Details |
125126
|-|-|

0 commit comments

Comments
 (0)