SALES: 1-800-867-1380
44 out of 67 rated this helpful - Rate this topic

Virtual Machine and Cloud Service Sizes for Azure

Updated: April 3, 2014

This topic describes the available sizes and options for the virtual machine-based compute resources you can use to run your apps and workloads. These resources are available to you as Windows Azure Virtual Machines (sometimes called “IaaS virtual machines” or “persistent virtual machines”), and Cloud Service role instances (web roles and worker roles). This topic also provides deployment considerations to be aware of when planning to provision or deploy these resources.

If you’re not sure whether to use Windows Azure Virtual Machines or Cloud Services, see the “Execution Models / Compute” section of Introducing Windows Azure for explanations that can help you decide.

For more details about the disks and images used in Windows Azure Virtual Machines, see Manage Disks and Images and Virtual Machines Pricing Details. For more information about virtual machine sizes for web roles and worker roles, see Configure Sizes for Cloud Services.

Virtual machines are now available in two tiers – basic or standard. Both types offer a choice of sizes, as shown in the following table. Additionally, text descriptions for sizes have been replaced with “A<number>” names for the sizes.

The following considerations might help you decide on a size:

  • A1 (formerly “small”) is the smallest size recommended for production workloads.

  • Select a virtual machine with 4 or 8 CPU cores when using SQL Server Enterprise Edition.

  • The A0 (formerly “extra small”) size is only available by using Windows Azure SDK version 1.3 or later.

  • Some of the physical hosts in Windows Azure data centers may not support larger virtual machine sizes, such as A5, A6 and A7. As a result, you may see the error message Failed to configure virtual machine <machine name> or Failed to create virtual machine <machine name> when resizing an existing virtual machine to a new size; creating a new virtual machine in a virtual network created before April 16, 2013; or adding a new virtual machine to an existing cloud service. See the topic Error: “Failed to configure virtual machine” on the support forum for a list of workarounds for each deployment scenario.

Basic Tier

Size CPU
cores
Memory Disk sizes –
virtual machine
Max. data disks
(1 TB each)
Max. IOPS
(300 per disk)

A0

Shared (0.25)

768 MB

OS = 127 GB

Temporary = 20 GB

1

1x300

A1

1

1.75 GB

OS = 127 GB

Temporary = 40 GB

2

2x300

A2

2

3.5 GB

OS = 127 GB

Temporary = 60 GB

4

4x300

A3

4

7 GB

OS = 127 GB

Temporary = 120 GB

8

8x300

A4

8

14 GB

OS = 127 GB

Temporary = 240 GB

16

16x300

Standard Tier

Size CPU
cores
Memory Disk sizes –
virtual machine
Max. data disks
(1 TB each)
Max. IOPS
(500 per disk)

A0

Shared

768 MB

OS = 127 GB

Temporary = 20 GB

1

1x500

A1

1

1.75 GB

OS = 127 GB

Temporary = 70 GB

2

2x500

A2

2

3.5 GB

OS = 127 GB

Temporary = 135 GB

4

4x500

A3

4

7 GB

OS = 127 GB

Temporary = 285 GB

8

8x500

A4

8

14 GB

OS = 127 GB

Temporary = 605 GB

16

16x500

A5

2

14 GB

OS = 127 GB

Temporary = 135 GB

4

4X500

A6

4

28 GB

OS = 127 GB

Temporary = 285 GB

8

8x500

A7

8

56 GB

OS = 127 GB

Temporary = 605 GB

16

16x500

The following considerations might help you decide on a size:

  • Web roles and worker roles require more temporary disk space than Windows Azure Virtual Machines because of system requirements. The system files reserve 4 GB of space for the Windows page file, and 2 GB of space for the Windows dump file.

  • The OS disk contains the Windows guest OS and includes the Program Files folder (including installations done via startup tasks unless you specify another disk), registry changes, the System32 folder, and the .NET framework.

  • The local resource disk contains Windows Azure logs and configuration files, Windows Azure Diagnostics (which includes your IIS logs), and any local storage resources you define.

  • The apps (application) disk is where your .cspkg is extracted and includes your website, binaries, role host process, startup tasks, web.config, and so on.

 

Size CPU
cores
Memory Disk sizes

ExtraSmall

Shared

768 MB

OS = Guest OS size

Local resource = 19 GB

Apps = approx. 1.5 GB

Small

1

1.75 GB

OS = Guest OS size

Local resource = 224 GB

Apps = approx. 1.5 GB

Medium

2

3.5 GB

OS = Guest OS size

Local resource = 489 GB

Apps = approx. 1.5 GB

Large

4

7 GB

OS = Guest OS size

Local resource = 999 GB

Apps = approx. 1.5 GB

ExtraLarge

8

14 GB

OS = Guest OS size

Local resource = 2,039 GB

Apps = approx. 1.5 GB

A5

2

14 GB

OS = Guest OS size

Local resource = 489 GB

Apps = approx. 1.5 GB

A6

4

28 GB

OS = Guest OS size

Local resource = 999 GB

Apps = approx. 1.5 GB

A7

8

56 GB

OS = Guest OS size

Local resource = 2,039 GB

Apps = approx. 1.5 GB

A8

8

56 GB

OS = Guest OS size

Local resource = 1.77 TB

Apps = approx. 1.5 GB

noteNote
For details about using this size to run Message Passing Interface (MPI) applications, see A8 and A9 Compute Intensive Instances: Quick Start with HPC Pack.

A9

16

112 GB

OS = Guest OS size

Local resource = 1.77 TB

Apps = approx. 1.5 GB

noteNote
For details about using this size to run Message Passing Interface (MPI) applications, see A8 and A9 Compute Intensive Instances: Quick Start with HPC Pack.

See Also

Did you find this helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft. All rights reserved.