x-ms-ratelimit-remaining-microsoft.consumption-tenant-requests : 12
x-ms-ratelimit-remaining-microsoft.consumption-clientAppId-requests : 60
For Azure Consumption Usage Details there is an API throttling limit of 12 per tenant.
how to increase this throttle limit.
Related
We are using a premium Azure Service Bus and we are getting close to our current limit of 5 GB into our current limit of 5 GB as the maximum topic size. We are considering increasing it to 10GB or 20GB but we cannot see what the implications will be from a cost and/or performance perspective?
Will an increase of topic size introduce extra costs or affect the general performance of the service bus (we are currently using one message unit).
We are building an Ecom app which will relay on Azure APIM, we expect 66.5 million requests per day. In a pick hours, it would be 10 million requests. Can Azure APIM Premium handle such a load? At present we have 8 scale units, is that sufficient?
According to the docs the estimated maximum throughput is 4000 rps. If you have 8 scale units the estimated maximum throughput is
32.000 rps
1.9m rpm
115.2 rph
You can have up to 12 scale units so you should be safe to handle such a load. (You can call to have > 12 scale units if needed)
I am trying to do cost calculation for the azure service bus premium tier. I could not found the answer to the following simple questions
What max message rate a single message unit can support
What max throughput(data size/sec) a single message unit can support
Service bus premium messaging does not impose message limit in terms of number in that way (except 1 message can be of max 1 MB, and queue/topic max size 80 GB). It acts more like a compute resource. Based on metrics, you should decide on scale up/down or use auto-scaling feature it has.
There are a number of factors to take into consideration when deciding
the number of messaging units for your architecture:
Start with 1 or 2 messaging units allocated to your namespace.
Study the CPU usage metrics within the Resource usage metrics for your namespace.
If CPU usage is below 20%, you might be able to scale down the number of messaging units allocated to your namespace.
If CPU usage is above 70%, your application will benefit from scaling up the number of messaging units allocated to your namespace.
To learn how to configure a Service Bus namespace to automatically
scale (increase or decrease messaging units), see Automatically
update messaging units.
For more details, refer this and this.
Will I be charged if I host my application on Azure App Service more than 60 min even if my app does not do any processing?
The answer is NO.
Under App Service -> App Service Plan -> Quotas you can see a detailed breakdown of usage such as an example below for a website I created hours ago but showing only 1.11 minutes of usage:
I got the answer from AjayKumar-MSFT's answer from this post at a Microsoft forum, then proceeded to test it myself.
You could go serverless with Azure Functions, host in a Consumption plan and only pay for execution time. It's a bit more complicated than that but in essence you don't pay for idle code, which i believe is what you're after.
https://azure.microsoft.com/en-us/pricing/details/functions/
Functions are billed based on observed resource consumption measured in gigabyte seconds (GB-s). Observed resource consumption is calculated by multiplying average memory size in gigabytes by the time in milliseconds it takes to execute the function. Memory used by a function is measured by rounding up to the nearest 128 MB, up to the maximum memory size of 1,536 MB, with execution time calculated by rounding up to the nearest 1 ms. The minimum execution time and memory for a single function execution is 100 ms and 128 mb respectively. Functions pricing includes a monthly free grant of 400,000 GB-s.
A very detailed example is found under that URL.
My answer is NO. if CPU time exceeds no charge will cost rather site will be stopped and it will be working after a certain time next day. Under App Service -> App Service Plan -> Quotas you can get details of CPU time and memory. It is clearly mentioned in Quotas that Applications hosted in a free or shared App Service plan are subject to usage quotas. If any quota is exceeded the site will be stopped until that quota resets. You can remove quotas on your app by scaling up your App Service Plan.
The costs depend on the pricing plan you choose for your app. There are several plans available to choose from. You could choose the Free plan and you won't incur costs but this plan is mostly meant for experimenting with the platform. It doesn't provide any SLA.
You can find more details about the pricing at the following links
App Service pricing
App Service Plans
And yes, your app will incur costs even if it is not consuming any CPU since it is allocated resource (a VM) and is running.
I already asked my question here in the comments, but I didn't received an answer - maybe because this blog is old & not many read it.
We have a Visual Studio Premium with MSDN - subscription.
Can someone answer?
Edit:
The actual question:
Is limit = fixed billing? I have a limit of 350 cores: Is there a difference in billing if I use 1 core or 350 cores?
Question 2: Why is in the limit overview no WebApp or SQL DB limit? Can I create unlimited amount of it? But then I have to pay for each one I create?
Is limit = fixed billing?
No, limit is not equal to fixed billing. Billing is based on the consumption while the limit defines the quota.
To take your example, you have a limit of 350 cores. What that means is that you can consume up to 350 cores in your subscription. You will be billed for the number of cores you consume (e.g. if you consume 10 cores, you will be billed for 10 cores only).
When it comes to limits, there are soft limits and there are hard limits. Soft limits are the default limits on your subscription when you sign up for an Azure Subscription. You can get the soft limits increased by contacting support. Hard limits are the limits in your Azure Subscription that you can't exceed. For example, currently there's a hard limit of 100 storage accounts per subscription. You can't go beyond those 100 storage accounts. If you need more storage accounts, then you would have to purchase a new subscription.