search

MicrosoftDocs / azure-docs

Open source documentation of Microsoft Azure
https://docs.microsoft.com/azure
Creative Commons Attribution 4.0 International
10.26k stars 21.43k forks source link

Question: What are the Image Analysis service Quota and Rate limits? #112469

Closed mattmazzola closed 9 months ago

mattmazzola commented 1 year ago

I am unable to find information about quota or rate limits for the Azure Vision Service. We have to run a potentially large set of requests (~2M) and are considering how we can parallelize this to decrease total running duration without hitting either limit.

Overall I would say there is a lot of mismatch of terms that cause confusion for customers. Here are examples:

Pricing Page

When I go to the Pricing - Computer Vision API | Microsoft Azure page it implies there multiple tiers of the service F, S1, S2, S3. image

Azure Portal - Overview

However, when I go to the Azure portal and provision a vision service I am only able to select S1 tier. It shows "Standard" on overview which isn't specific enough

image

Azure Portal - Pricing

Then more confusion is when I go to the pricing on actual resource it says S0

image

As I understand pricing is this "$1.00 USD/1K calls"

I would like to know the quota and rate limits.

I expect Quota to be maximum requests for longer time periods such as 100k requests / 1 day or similar I expect Rate Limit to be maximum request for shorter time period such as 10k requests / 1 min or similar

If this information does exist can you provide a link to it? If this information does not exist, I suggest to add it to the documentation and consolidate/normalize the service tier terms. It seems like at one point that had separate tiers and now it's all a single standard tier but the documentation is not updated.

Document Details

⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

AjayBathini-MSFT commented 1 year ago

@mattmazzola Thanks for your feedback! We will investigate and update as appropriate.

RamanathanChinnappan-MSFT commented 1 year ago

@PatrickFarley

could you please review this and update as appropriate.

RamanathanChinnappan-MSFT commented 1 year ago

@mattmazzola

I've delegated this to @PatrickFarley, a content author, to review and share their valuable insights.

mattmazzola commented 1 year ago

I've delegated this to @PatrickFarley, a content author, to review and share their valuable insights

Normally issues are closed by submitting a pull request which resolves the issue. In this case it seems you have closed the issue before it has been resolved, simply because someone was assigned to it.

If there is a PR which updates the documentation, can you share a link to it? If there is not a PR, can you answer the open questions here.

dbish commented 10 months ago

I have the same situation and same question. Quite confusing going between the docs and actually enabling this resource in the service. I don't see an answer here or a fix to the docs in this timeframe. What's the answer?

PatrickFarley commented 10 months ago

@RamanathanChinnappan-MSFT why was this issue closed?

RamanathanChinnappan-MSFT commented 9 months ago

@PatrickFarley I have reopened the case it was closed mistakenly i apologies for it.

PatrickFarley commented 9 months ago

@RamanathanChinnappan-MSFT Thank you. I'm noticing that none of the docs pages I own are affected by this; these are all pages on the Azure portal. Do you know who is responsible for that content?

Anyway, I've asked a dev lead about which pricing scheme is right

PatrickFarley commented 9 months ago

The team is working on getting the ACOM pricing page updated. To answer the question here: The S1,2,3 shown on the pricing page do not correspond to individual SKUs. They are showing how the S0 (standard) SKU prices the different Vision operations. There are different pricing schemes for different operations.

please-close

dbish commented 9 months ago

Thanks. Just a small note, imho you shouldn't close an issue until it's resolved, which in this case means the pricing page is appropriately updated ("done done") so the customer (me or Matt here in this case) can actually see the change and solve the problem.

dbish commented 8 months ago

Noting here, this was "resolved" but never fixed and it's now 2/19/2024 with no change to the docs