What is the main difference between "Extra Large and A5 instances" in Azure? I can see that there is a difference in CPU cores and also a mention that you must use A5 for "memory" intensive operations. I understand memory intensive as a word, but why would IIS be hosted in 2 cores (A5) when there is a choice for 8 cores (Extra Large) (with the same 14 GB RAM)?
Asked
Active
Viewed 490 times
-1
-
How can anyone tell you whether or not your custom app that you've developed and we've never seen is memory intensive? – MDMarra Jan 29 '14 at 00:30
-
@MDMarra - rephrasing my question again - "Intention of the question not to ask where should I host my IIS, but to understand the differences between two editions of Azure VM and in general is IIS suitable to be run in which edition of VM (A5 or XL)". I never asked abything about my application, only asked what is the difference between XL and A5 instances. Edited the question for that effect – VJVRR Jan 29 '14 at 00:48
1 Answers
0
The MSDN page Virtual Machine and Cloud Service Sizes for Windows Azure perhaps makes this more clear.
You can see from the table that in all aspects (CPU, disk, IOPS, etc.) the A5 instance is sized identically to the Medium instance, except that it has four times as much RAM. The same for A6 versus Large, and A7 versus Extra Large.
You would use such an instance if your application is truly memory-intensive, and needs fewer of other resources such as CPU and disk in relation to memory. Whether that is true of your application is something you will have to figure out for yourself.
In my experience it's not typical of web sites to be memory bound; they usually are CPU or I/O bound. I would not consider a memory intensive VM unless I knew the web app needed far more memory than is typical of a web site.
Michael Hampton
- 237,123
- 42
- 477
- 940
-
appreciate the time taken to understand the question and respond and for the hyperlinks. Gave me much needed clarity. Thanks and cheers. VJ – VJVRR Jan 29 '14 at 04:11