Azure Service Plan - Scale out charges - azure

Do i need to pay twice the monthly charges (56$/month) if I "scale out" my basic service plan to 2 instances ? Or price is inclusive up to 3 instances ?

You'll be charged per instance when you scale out. So two instances will be $112/month, and three will be $168/month.

As Rob Reagan mentioned that it will be charged per instance. We can get the price via azure pricing calculator. More details please refer to the screenshot.

If you are not going to use the 3 capabilities full time, program the horizontal scale of your service to use at least 1 to 3 instances when you reach a certain parameter you can choose. This way you will pay for the additional machines only for as long as they are needed.

Related

How azure served app service handle scale up in price?

I am thinking of purchasing a 3 year reserved app service plan on azure.
For my site, normally 1 or 2 instances are just good enough, but in the busy time, I have rules to autoscale the site out to 10 instances.
If I buy a 3 year reserved app service plan and my site auto scale out, will I be charged by the reserved price or pay as you go price?
from their doc, my feeling is that I will be charged by pay as you go price.Is it right?
You are right, the reservation agreement is just a discount that will apply to the number of running instances that match the reservation scope and attributes. So any extra instances will be charged using your standard rate.
This rate will depend on the type of subscription you use for paying for the reservation. If you have an individual pay-as-you-go subscription, extra app services will be charged by pay-as-you-go price. However, if you have an enterprise agreement, the price will be different and will depend on the agreement.

EP1 instance costs in function App Premium Elastic Plan w.r.t. Scale-up and Scale-out settings

Can anyone please elaborate me the minimum and miximum price of below settings(for reference) while creating the FunctionApp in Premium Elastic plan(EP1).
Q. How does Plan Scale out
Minimum Instances,
Maximum Burst and
App Scale out
Pre-Warmed Instances settings of FunctionApp affects costs?
For your question, I summarized the pricing rules below for your reference:
Azure Functions Premium plan provides the same features and scaling mechanism used on the Consumption plan, but the difference is we can set the Pre-Warmed instances.
Premium plan can avoid cold start by setting the Pre-Warmed instances, for example we can set 1 instance for Pre-Warmed(but smaller than minimum instances size which you set), then if the function app hasn't been requested for a long time, we just need to pay for the warm instance. The price is shown as below:
The EP1 plan is 3.5GB for each instance, so we can calculate the price.
While the function app is requested, then it will billed on a per second basis based on the number of vCPU-s and GB-s(based on the number of the instance which your function app uses on a per secnond).
Hope it would be helpful to your question~
I got the answer: here
"You are charged for each instance allocated in the minimum instance count regardless if functions are executing or not."

Is there any way to see estimated Azure costs before actually using the services?

Right now I have a small web app hosted on Azure services. Its 5 asp.net pages, 1 sql DB, and 2 scheduled jobs. Just through testing, I used 2 dollars of the 220 dollars credit they give you for signing up.
The problem I'm having is that there is no clear pricing guide for the pay-as-you-go service they offer. My live testing was very very lightweight (10 page hits, maybe 50db transactions, and 10 job runs) and its already cost 2 dollars. The breakdown available makes it clear where that money has gone (the scheduled jobs), but doesnt make it clear how much additional usage may cost me going forward.
Is there any area in azure, or any service anywhere, that can estimate the total cost under various loads? I am very hesitant to open this service up to the public until I know exactly what the costs will be, as right now the site brings in 0 revenue, so it wouldnt be worth paying a ton of money just for hosting until I get a revenue model set up.
Sure - use the Azure pricing calculator - http://azure.microsoft.com/en-us/pricing/calculator/

3 Months Windows Azure Trial Disabled in 3 Weeks

My 3 months trial account Windows Azure has already been disabled in 3 weeks. How's that possible? I had nothing on my project, just a simple Asp.Net web page.
I don't think anybody knew my page and made constant requests.
I can't find a statistics section on Management Portal to check what was my traffic...etc.
Does anybody know where I can check my Hosted Service's statistics?
Thanks
The trial provides 750 compute hours monthly. Once you deploy your app, the meter is ticking. That is, as long as something is deployed, it's a metered resource. Whether consuming 0% or 100% cpu/network/memory, you pay hourly.
Now: If you deployed a single Small instance for your asp.net site, you shouldn't have consumed 750 hours in 3 weeks. Is it possible you deployed with Medium instances? Or deployed with 2 Small instances? Do you have more than one Role in your deployment (since each would have at least one instance)?
One bit of advice I give, when doing dev work: at the end of the day, when you're not actively working on a project, delete the deployment (you can always re-deploy to the same place later). This helps save tremendously on consumed hours.
You aren't charged based on access to a hosted service (i.e. compute instance). As long as you have something deployed there, you are charged. No one can ever go to it and it still costs you money.
At the portal, you have to delete whatever hosted services you have there in order to preserve credits. For example if you had up both a Production and a Staging instance, they would charge you compute hours for both. You have to actually delete the instances in order to conserve compute hours on your bill.
As for stats, the only way you can get access stats that I know of is by using the azure diagnostics features. They used to have a lot more detail on their bills (in / out transfers, etc) but the bills are a lot shorter now.

What about expenses on unused resources in Windows Azure?

The main question is: do I have to pay for unused resources? For instance, Azure pricing calculator says approximately $30/month for XS box. This includes about 750 hours. What if I don't use them all? This is normal for early stage, while development is in progress.
This is just to make it clear if its cheaper to have a virtual hosting for development and beta-testing purposes.
Not exactly a programming question.
That said: Windows Azure Compute instances are metered by the hour, and metering happens when you have deployed instances (whether running or stopped). If you're doing dev work, deploy for an hour or two (or how long it takes you to test), then delete the deployment. Very easy to delete, very easy to redeploy. Just don't delete the actual hosted service definition (urlname.cloudapp.net, associated certificates, affinity group, etc.). Following this pattern, it's easy to test with 5-10 concurrent instances in a deployment throughout the month - just remember to delete the deployment after each test cycle.
#Bart is partially right about SQL Azure being billed for the month. It's actually amortized daily. This also means: If you set up a 5GB db and only have 99MB on a given day (or days), you're billed at the $4.999 monthly rate / # of days in month). That's about 17 cents daily if you stay under 100MB. And if you delete the db, you're no longer billed.
Same goes for Cache - the cost is amortized daily.
I'd look at the full pricing page here.
You do not have to pay for unused resources in SOME of the services.
In your example, if you deploy a website for 10 hours you will be billed for the 10 hours of usage. PLUS any transactions/bandwidth associated with it.
However, some the services do have a flat fee. For example, if you deploy a 5 gig DB to SQL Azure and u do not use it...u will be billed the monthly rate even if it just sits there.
Also your definition of "use it" needs to be clear. Azure will bill you, if you have ANYTHING deployed. Even if the VM is stopped, you are getting billed. Therefore, the best solution is to:
- monitor your usage (its updated multiple times per day)
- use a free trial, MSDN account or promotion to see what the charges will be
- call MIcrosoft...Azure is the hot thing now and they WILL give you a break on charges if they are within reason.

Resources