i have standard(s0) account on microsoft azure platform, i am trying to make an application to recognize faces from the images. this application will be used by many people simultaneously, currently we have limitation of 10 transaction per second in standard account that means if 10 concurrent user will try to make request at same time, the application will fail. is there any method to solve this problem.
https://azure.microsoft.com/en-us/pricing/details/cognitive-services/
As per pricing, maximum you can have is 10 transaction per second. According to my knowledge there is no way to handle this as of now. You might need to ask for support from Microsoft inorder to achieve this.
For this request ,this is Microsoft Cognitive support team's reply : you can follow this guide to raise a support ticket , and Azure support team will increase TPS(Transaction Per Second) limit for you based on your past TPS call and then decide on the promotion.
Related
I created my Free Azure subscription and have been hosting a couple of Apps out there since around April of this year (2020).
All of my resources; Subscription, Resource Group, AppService, and Apps are F1 service rather than S1 to ensure they are running free and my cost forecast for the month should always say $0.0. This was something confusing in the beginning that I had to reach out to Microsoft to help me with in setting up my hierocracy of resources.
In my main web app I now need to deploy an SQL Database. I've been developing using LocalDB in my ASP.Net Core 3.1 app.
Now the Free Azure description here:
https://azure.microsoft.com/en-us/free/
gives these specs for SQL Server with your free subscription for the first year:
250GBs. Now I'm thinking 250GB of storage, not memory. But when you start selecting your DB configuration they are talking memory. So now I'm confused with that. Do you get 250GB of Storage or memory with free SQL Server with free Azure subscription.
Also, the free service really just says free SQL Database. Not free SQL Server. So I am confused here as well. Do you just get one Database? I know you have to set up an SQL Server in order to set up the Database.
Next I found a quick tutorial on creating an SQL Server Database her:
https://learn.microsoft.com/en-us/azure/azure-sql/database/single-database-create-quickstart?tabs=azure-portal
I want to go through the three versions of this tutorial:
Using:
Portal
Azure CLI
PowerShell
so I can get a feel for the environment and find the way that best suites me.
I am going through the Portal tutorial first.
On step 9, the default is General Purpose, Serverless.
This says "up to 40 vCores, up to 120 GB memory".
But you are supposed to have 250GBs with the free subscription.
So this is not it.
I click provisioned and now it says "up to 80 vCores, up to 408 GB memory".
Well 408GB is too much; over 250GB.
So I click, "Looking for Basic, Standard, or Premium?"
And from there click Standard because it is the 250GB configuration I think I am looking for to get the free SQL Database with the free Azure Subscription. (Again do I just get one database?)
But now instead of talking vCores, the cost is per DTU. What the hec is a DTU? I tried to read up on it. Seems like a unit of performance rather than a transaction. So standard is estimated at 10 DTUs a month I believe. Hopefully that does not mean 10 transactions per month but rather again a measure of performance.
Estimated Cost $15 dollars a month.
That "Standard S0" above scares me I think that would start charging me.
It should say F1 shouldn't it.
I've come accross some similar questions to this online. A lot of people seem to have the same confusion and question I have. Main question is how do I get an F1 level database for my app. And is one database all I get. That would suck. Not really a free subscription then since most web apps in ASP.Net/Core which is Microsoft are dynamic and need a DB and Azure is Microsoft right?
Or should I just go ahead and review and create. And S0 is just how they do it for free Azure subscription? Like you wouldn't get charged for S0? But I don't think so.
Trying to get a concrete answer somewhere so I know how to proceed.
UPDATE 10/20/20
I have just gone in a different way and am creating an SQL Server instead of Sql Database.
This appears to be free and cost estimate per month says:
"No extra charges"
Ok everybody.
Let's consider this a tentative answer until it all proves out to be true.
I opened up a support ticket with Azure/Microsoft.
Here is part(s) of the response I got:
First, I would like to thank you very much for providing me with such a detailed service request. After my investigation, I was able to determine that the estimated price does not show the discount with the free services. Therefore, using the S0 database in Azure SQL Database at the Basic service tier will be included in the free services. The free service limitation states that you can use up to 250 GB. So, anything deployed below 250 GB is ok to use if it is correctly configuring all around. As long as you stay within the limits, you're will not be charged.
My reply here:
So thank you for the information on S0 being considered free as part of the F1 subscription.
(Although, I really wish they would include next to S0 on the pricing sheet to use as part of F1 in parenthesis or something)
Does it matter if you use vCores or DTUs?
And if you use DTUs does it matter if you go above the max?
Or as you said I guess as long as I stay under 250GB I'm ok.
Her response continued:
Lastly, I would like to leave you with a link on how to avoid charges on your free service account: https://learn.microsoft.com/en-us/azure/cost-management-billing/manage/avoid-charges-free-account.
I hope this information was beneficial to you, Sam. Please let me know if you have any additional questions.
Everybody notice the link to track your free services which enables us to make sure we do not use a service outside of the free services or exceed the amount of what we get with a free service. I think this is a gold mine find of a URL.
And one more question I sent her:
Can I create a 250GB application for each app I deploy out there.
Or do I only get one and have to make all my apps share it?
At least we know that Basic S0 is free now.
I will update this answer with better information as I work through the details.
This is the best answer.
I have worked out a procedure that works for me.
And I understand a lot of things better now.
It seems like the whole answer is not in one place since Azure is so vast and everyone's
scenario is different.
So I wrote up an article to document what worked for me.
I hope this helps someone out there:
https://ctas.azurewebsites.net/TechCorner/AspNetCore3/HowTos/DeployWebAppWithLocalDbToAzure
The documentation for the Azure Face API says that the limit for faceIds in a call to Group is 1000. See: https://westeurope.dev.cognitive.microsoft.com/docs/services/563879b61984550e40cbbe8d/operations/563879b61984550f30395238
Is there any way to raise this limit or another way to achive grouping of more than 1000 faces?
I'm afraid not, the limit of this api is still 1000 faces. You can vote up for this feature on the feedback page. The develop team may improve the limit in the future.
This question already has answers here:
Did Instagram change API rate limits on Mar 30, 2018?
(5 answers)
Closed 4 years ago.
Does anyone have any clue why Instagram has reduced their hourly API request limit from 5000 to just 200? Is this a bug or the new normal? Do instagram partners undergo the same lowering of rate limit?
The page on rate limits in the documentation is a broken link.
:::UPDATES FROM INSTAGRAM via MAIL:::
To summarize, Basically Instagram API is shutting down faster than speed of light right now. Migrate your apps to FB-instagram-API to keep your business or apps running
Yes, from what I think are updated Facebook docs.
Rate Limiting
The Instagram API uses the same rate limiting as the Graph API (200 calls per user per hour) with one exception: the /media/comments edge limits writes to 60 writes per user per hour. Please refer to the Graph API's rate limiting documentation for more information.
Facebook documentation
Seems to be in relation to trying to clean up privacy and user data usage.
TechCrunch article - https://techcrunch.com/2018/04/02/instagram-api-limit/
Without warning, Instagram has broken many of the unofficial apps
built on its platform. This weekend it surprised developers with a
massive reduction in how much data they can pull from the Instagram
API, shrinking the API limit from 5,000 to 200 calls per user per
hour. Apps that help people figure out if their followers follow them
back or interact with them, analyze their audiences or find relevant
hashtags are now quickly running into their API limits, leading to
broken functionality and pissed off users.
Two sources confirmed the new limits to TechCrunch, and developers are
complaining about the situation on StackOverflow.
I am trying to understand how Azure Mobile Services scaling work.
Below screenshot was taken from Mobile Services scale tab in Azure portal.I am using BASIC tier.
When setting SCALE-BY METRIC to NONE, we will pay at a "minimum" UNIT COUNT * $14.99.
For example, if i set UNIT COUNT to 6, then I'll pay 6 * $14.99 = $89.94 every month no matter how much API calls are being made, is my understanding correct?
When setting SCALE-BY METRIC to API CALLS, we can set minimum UNIT COUNT and maximum UNIT COUNT, this is suitable if at some days we have few api calls but in other days we have more api calls, is this correct?
Before moving from development to production, how do we anticipate which scaling option to use? Continuously monitor the API count and change the scaling option when we think we will go over the limit?
thanks!
I'm not affiliated with MS or Azure, so these answers are from my personal understanding.
Yes this is my understanding as well. You can also check this behaviour by extrapolating the predicted costs in your bill.
Yes.
I have a few apps running on Windows Azure Mobile Services in the Store. Usually I start out by trying to estimate the typical api calls per session. This can be done quite easily as long as you are in development. This should give you an idea about how many users an instance can support. Example: In one of my simpler apps one instance could serve about 800-1000 daily active users. Now, even with this information I usually set the scaling to the maximum for launch day, just to anticipate anything. In case it scales to the maximum it'll most likely be just for a day - and if it isn't well in that case congrats!
I am writing a Java application that needs to get images from Google image search (or similar).
It works as simple as a web call:
http://ajax.googleapis.com/ajax/services/search/images?v=1.0&q=japan
However, the response is limited to 8 results per page.
and google search is free for only 100 requests per day, so 800 results per day.
Is that correct?
The replacement for that deprecated API is here: https://developers.google.com/custom-search/v1/overview and for billing they note:
Any usage beyond the free usage quota will fail if you are not signed up for billing. Once you have enabled billing, you will continue to receive 100 free queries per day. However, you will be billed for all additional requests at the rate of $5 per 1000 queries, for up to 10,000 queries per day.
So the alternative is, simply, to pay for what you need.
There is lots of information from a similar question here: What's the best web image search API?
Somebody on that thread notes:
As of August 2012, Bing API will be part of Azure Marketplace: free access still available, but limited to a number of queries (5000/month). Google limits the free access to 100 queries/day.
So perhaps Bing has sufficient free quota for your needs? There are other options on that page also, check it out.