You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: includes/storage-blob-scale-targets.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -17,4 +17,4 @@ ms.author: tamram
17
17
| Maximum number of stored access policies per blob container | 5 |
18
18
|Target throughput for single blob |Up to storage account ingress/egress limits<sup>1</sup> |
19
19
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