Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Is the "Target throughput for single blob" notation gone? #27901

Closed
YuKogasaka opened this issue Mar 25, 2019 — with docs.microsoft.com · 5 comments
Closed

Is the "Target throughput for single blob" notation gone? #27901

YuKogasaka opened this issue Mar 25, 2019 — with docs.microsoft.com · 5 comments
Assignees
@roygara
Labels
assigned-to-author product-question storage/svc triaged

Comments

@YuKogasaka docs.microsoft.com
Copy link
Contributor

YuKogasaka commented Mar 25, 2019 •
edited
Loading

The document has been updated on 03/23/2019, but at that time the description of "Target throughput for single blob" was lost.

@@ -14,5 +14,4 @@ ms.author: tamram
| Maximum size of a block in an append blob | 4 MiB |
| Maximum size of an append blob | 50,000 x 4 MiB (approximately 195 GiB) |
| Maximum size of a page blob | 8 TiB |
'-' | Maximum number of stored access policies per blob container | 5 |
'-' | Target throughput for single blob | Up to 60 MiB per second, or up to 500 requests per second |
'+' | Maximum number of stored access policies per blob container | 5 |

Did you have any problems?

// Describes to the customer what has previously been described about Blob Storage performance, but is puzzled by the removal.

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
@YASWANTHM-MSFT
Copy link

@kogesaka, Thanks for your question. We are actively investigating and will get back to you soon.

@SumanthMarigowda-MSFT-zz
Copy link
Contributor

@roygara Kindly add your comments on the above mentioned query

@SumanthMarigowda-MSFT-zz SumanthMarigowda-MSFT-zz removed their assignment Apr 4, 2019
@roygara
Copy link
Contributor

roygara commented Apr 11, 2019

@kogesaka Thanks for reaching out. It was removed because with the addition of high throughput block blobs and premium block blobs the original statement doesn't make sense/ doesn't really apply. We'll be updating it with new language soon.

@YuKogasaka
Copy link
Contributor Author

@roygara, thank you for comment. I understand the contents.

There are many questions (especially in Japan) that the listed performance values ​​do not come out, so I think this decision is correct.

There is no problem with closing this issue as I wait for the update to be done in Japanese.

@YASWANTHM-MSFT
Copy link

@Kogesaka, we will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly reopen the issue and continue the discussion

@mockodin mockodin mentioned this issue Dec 24, 2020
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@roygara roygara

Labels
assigned-to-author product-question storage/svc triaged
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@YuKogasaka @PRMerger9 @roygara @YASWANTHM-MSFT @SumanthMarigowda-MSFT-zz