Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion includes/storage-blob-scale-targets.md
Original file line number Diff line number Diff line change
Expand Up @@ -16,7 +16,7 @@ ms.author: normesta
| Maximum size of an append blob | 50,000 x 4 MiB (approximately 195 GiB) |
| Maximum size of a page blob | 8 TiB<sup>2</sup> |
| Maximum number of stored access policies per blob container | 5 |
| Target request rate for a single page blob | Up to 500 requests per second |
| Target request rate for a single blob | Up to 500 requests per second |
| Target throughput for a single page blob | Up to 60 MiB per second<sup>2</sup> |
| Target throughput for a single block blob | Up to storage account ingress/egress limits<sup>1</sup> |
Comment on lines +19 to 21
Copy link

Copilot AI Feb 19, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The updated wording (“single blob”) is ambiguous in the context of the surrounding rows that remain blob-type-specific (page vs block). If 500 rps truly applies to all blob types, consider explicitly stating that (e.g., ‘single blob (block, append, or page)’) and/or adding a supporting footnote/source. If the target request rate differs by blob type, the table should include separate request-rate entries for block and append blobs (not just page) to avoid implying uniform limits.

Copilot uses AI. Check for mistakes.

Expand Down