Skip to content

Commit 4c7f3c7

Browse files
authored
Merge pull request #31301 from clausjor/patch-1
Update storage-blob-scale-targets.md
2 parents ecd467b + 639eec8 commit 4c7f3c7

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

includes/storage-blob-scale-targets.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -17,4 +17,4 @@ ms.author: tamram
1717
| Maximum number of stored access policies per blob container | 5 |
1818
|Target throughput for single blob |Up to storage account ingress/egress limits<sup>1</sup> |
1919

20-
<sup>1</sup> Single object throughput depends on several factors, including, but not limited to: concurrency, request size, performance tier, speed of source for uploads, and destination for downloads. To take advantage of [high-throughput block blob](https://azure.microsoft.com/blog/high-throughput-with-azure-blob-storage/) performance enhancements, use a Put Blob or Put Block request size of > 4 MiB (> 256 MiB for premium-performance block blob storage or for Data Lake Storage Gen2).
20+
<sup>1</sup> Single object throughput depends on several factors, including, but not limited to: concurrency, request size, performance tier, speed of source for uploads, and destination for downloads. To take advantage of [high-throughput block blob](https://azure.microsoft.com/blog/high-throughput-with-azure-blob-storage/) performance enhancements, use a Put Blob or Put Block request size of > 4 MiB (> 256 KiB for premium-performance block blob storage or for Data Lake Storage Gen2).

0 commit comments

Comments
 (0)