Merge pull request #104021 from roygara/upDate

Updating upload target

Author: PRMerger12

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

@@ -83,7 +83,7 @@ To help you plan your deployment for each of the stages, below are the results o
 | Number of objects | 25 million objects |
 | Dataset Size| ~4.7 TiB |
 | Average File Size | ~200 KiB (Largest File: 100 GiB) |
-| Upload Throughput | 20 objects per second |
+| Upload Throughput | 20 objects per second per sync group |
 | Namespace Download Throughput* | 400 objects per second |
 
 *When a new server endpoint is created, the Azure File Sync agent does not download any of the file content. 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.
@@ -93,7 +93,7 @@ To help you plan your deployment for each of the stages, below are the results o
 | Number of objects synced| 125,000 objects (~1% churn) |
 | Dataset Size| 50 GiB |
 | Average File Size | ~500 KiB |
-| Upload Throughput | 20 objects per second |
+| Upload Throughput | 20 objects per second per sync group |
 | Full Download Throughput* | 60 objects per second |
 
 *If cloud tiering is enabled, you are likely to observe better performance as only some of the file data is downloaded. Azure File Sync only downloads the data of cached files when they are changed on any of the endpoints. For any tiered or newly created files, the agent does not download the file data, and instead only syncs the namespace to all the server endpoints. The agent also supports partial downloads of tiered files as they are accessed by the user.