Hi I need to buy a subscription in azure with two DB and 1 Basic App.
Anyway I don't understand what stand for instance * hours.
I wrote an B2B site in aspnet that has to be run in this subscripotion.
How can I calculate or know how many instances I need?
And how do you calculate the hours for instance?
Is possible set it scalable?
For starters, there are 4 question in this question.
Well, instance * hours means you will have to pay X of some currency for every hour or every instance working. So 1 instance working for 20 hours = 20 hours billed, 5 instances working for 20 hours = 100 hours billed.
Hours are calculated pretty straight forward, once you've created App Service Plan you are being billed constantly, until you delete it.
Yes, WebApp's are scalable. And for the How can I calculate or know how many instances I need? we can't help you. It depends on your load. You would need to do some performance testing emulating actual load.
Also, check out the pricing calculator.
edit in Instances: So when you create a WebApp it has 1 instance initially. Instance is a VM hosting IIS that is hosting your WebApp. When you scale it, you create additional instances (VM's) that host additional IIS instances that host copies of your WebApp.
Related
why managed instance taking more time to create?
It has been almost two days managed instance creation started and it is still showing deployment under progress. This is the first time I'm creating MI. Does anyone know how long will it take to create?
Very basic specification: Gen4 8 core 256 memory location: south central us
I don't see any error yet.
Creating first instance within a subnet takes few hours as Managed Instance is customer VNet-injected service and it takes time to provision the whole dedicated cluster - it's much more work than taking random pre-provisioned VM and spinning up few processes on it.
That said, anything that takes more than 6 hours (at the moment, subject of improvement) indicates some sort of issue.
I'd suggest opening support ticket, or you can contact me via private message with more details for the specific instance.
Two days is excessive, and likely indicates a bug in Azure's back-end scripts. When provisioning large amounts of objects in your Azure subscription, you can run out of resources within your 'Ring', which is a pre-allocated set of resources you have to work with. In the event you've exhausted these resources, it does take some time for Azure to provision more before the managed instance can be created.
I've deployed 10 or so Managed Instances and have seen deployment time take anywhere from
1 to 8 hours for a healthy deploy, and over a day for a deploy that ran into a bug.
Right, so some time ago I requested access to the N Series instances with gpu.
Don`t know what happened but when I try to create a new W. 2012 R2 datacenter server I have the option to create an NC6. I configure the whole thing and at the end it tells me I have ZERO cores available.
I have 2 types of subscription. Pay as You Go and Free Trial. Pay as You Go has a remaining of 10 cores and I have no other instance created.
How can I fix this? I really need around 30-40 hours time of one of those instances for an important project of mine that requires intense 3D capabilities.
You have to signup for this preview on http://gpu.azure.com/
My Azure websites are down a lot, four outages (30 minutes - 3 hours) in the past 30 days. I only use one small standard website and one web SQL DB in US West so I can't expect 99.5%. This week (a few days ago and currently), 503 errors were / are the problem, but I also experienced substantial DB downtimes at other occasions.
My question is: what can I do (with hopefully not too much additional costs and effort) to raise stability? Which measures did other Azure users try? Would this have prevented the 3 hour downtime last Monday?
There are (at least) three things you can do:
Scale your website so that you have 2 instances running (How to Scale Websites);
Deploy a another copy of the website in a different region, and use traffic manager to Load Balance them (Traffic Manager Overview)
Create another instance of the database, and sync them (Getting Started with Azure SQL Data Sync)
I'd like to point out that with Websites, you get a 99.9% availability for websites running is Basic and Standard mode regardless of the number of instances deployed. You can view the SLA document here: http://go.microsoft.com/fwlink/?linkid=301329&clcid=0x409
Regarding the 503 errors you experiences, this was an intermittent issue http://azure.microsoft.com/en-us/status/#history
I subscribed to free 90 days azure trail offered by MS. I was excited and talked about it everywhere(including my blog http://techibee.com/windows-2012/free-try-windows-server-2012-in-azure-for-90-days/1876) about the free service offered by MS and how to make use of it. Well, my excitement lasted only for 7-8 days. Today I got a message from Azure team that my subscription disabled as my computer hours exceed the monthly limit.
I am just wondering how these compute hours are calculated in my case. I configured 2 VMs(2 medium) and using them to explore stuff. I never shutdown them since creation. Anyone has idea how these two VMs constituted to limits.
Another question I have is, since the subscription is disabled for this month, I am considering purchasing few more compute hours(pay-as-you-go). If I do that now, should I shutdown the VMs when I am not using them actively? will it stop the compute hours from increasing or they will continue to charge me for even shutdown hours. All I want is, I should get billed only when I am actively using it, when I am not connected to that host, I shouldn't. Looks like this is not happened in the trail program and their calculations seems different. Can anyone here given me some clarity?
From http://www.windowsazure.com/en-us/pricing/details/#header-3
Compute hours are charged whenever the Virtual Machine is deployed,
irrespective of whether it is running or not.
That's where all your hours went. You need to delete your VMs to prevent them using compute time.
With the free trial account you can configure only 1 VMs medium. Probably your offered expired early becouse you configured two.
Be aware that if you create a VM and you turn it off you will be charged the same as indicated when your turn off a VM.
I'm an msdn subscriber and I'm looking at Azure as a possible platform for a new website that will test the water of a new service. This website is expecting low to very low traffic at the time of launch. I've heard that this kind of traffic levels is very expensive for Azure but since they have this msdn offer, I thought I'd finally take a look at Azure.
In the offer, I'm looking at getting "750 small compute hours per month". From the reading I've done, this seems that, if I purchase nothing more than what's given (although the subscription itself is thousands of dollars of course), that an entire month would be covered. Since 24 (hours) x 31 (max days in a month) = 744 I'm still below my allotted 750 for the month.
Am I missing something else from this simple equation? Is there further aspects that could cause the site to be "turned off" temporarily that should be considered?
Yes, you can indeed run a small instance during a whole month. Or you can have 2 extra-small instances instead (having 2 instances means you're covered by the SLA).
There are 2 other things you need to consider:
Depending on your subscription you can have maximum 45GB of storage (blob/table/queue). If you use Virtual Machines you need to know that the system disk (and additional data disks) are persisted as blobs, so make sure not to reach the limit here.
There are also other limits active, but the most important one besides storage is the data transfer limit which is also very limited (max 35GB out).
If you're expecting very low traffic, did you ever consider Windows Azure Web Sites? You get 10 of those for free during 12 months. The free ones run on shared instances, but they are perfect to host the first low-traffic version of your app.