Update storage-blob-scale-targets.md#128213
Update storage-blob-scale-targets.md#128213HarukaMatsumura wants to merge 1 commit intoMicrosoftDocs:mainfrom
Conversation
Target request rate supposed to apply to all blob types
|
@HarukaMatsumura : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
|
Learn Build status updates of commit 345e70c: ✅ Validation status: passed
For more details, please refer to the build report. |
There was a problem hiding this comment.
Pull request overview
Updates the Azure Storage blob scalability targets documentation to clarify the intended scope of the “target request rate” entry (blob-wide rather than page-blob-only).
Changes:
- Rewords the request-rate row from “single page blob” to “single blob”.
- Keeps existing throughput rows scoped to specific blob types (page vs block).
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| | 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> | |
There was a problem hiding this comment.
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.
|
Can you review the proposed changes? IMPORTANT: When the changes are ready for publication, adding a #label:"aq-pr-triaged" |
prmerger-automator
bot
added
the
aq-pr-triaged
3 participants
Previously, the target request rate was applied to all blob types. However, in the most recent change, it appears to have been restricted to page blobs only. At the same time, when reviewing the commit, it seems that the word “page” was added merely to adjust the wording of the line, and the technical background for limiting the target request rate to page blobs is unclear.
Isn’t the target request rate supposed to apply to all blob types, as it did before the change? If the value of 500 requests per second truly applies only to page blobs, then please add information about the target request rates that apply to block blobs and append blobs as well.