Windows Azure Virtual Machine (24) uses premium storage and DS series VMS

Windows Azure Platform Family of articles Catalog

　　

This article describes the domestic azure China by the century connected operation

　　Readers familiar with the Azure platform understand that the IOPS per disk of Azure VMS is 500. We take the D-series VMs as an example, and the IOPS information is as follows:

virtual machine type	CPU	RAM	temp disk	number of external disks	IOPS
D1	1	3.5GB	50GB	2	2 * $
D2	2	7GB	100GB	4	4 *
D3	4	14GB	20 0GB	8	8 *
D4	8	28GB	400GB	16	*
D11	2	14GB	100GB	4	4 *
D12	4	28GB	200GB	8	8 * $
D13	8	56GB	400GB	+	*500
D14		112GB	800GB	+	+ * $

　　It is important to note that when creating an azure VM, the user does not keep all the virtual machine disks in the same storage account. Because a storage account has an IOPS limit of 20000.

In my personal experience, I recommend using the same storage account for every 3 VMS, and a 4th virtual machine using another storage account.

Premium Storage Premium Storage is required when we need higher IOPS, such as some scenarios that require higher performance disk reads and writes.

Traditional standard Storage (Storage) uses SSD (solid state Drives, SSD) for HDD (hard disk Drives, HDD), Premium Storage (Premium Storage)

Use premium Storage (premium Storage) to increase iops and throughput and reduce latency. Each VM can be configured with up to 32TB of persistent storage, each VM can exceed 50000 ioPS, and read operations have a delay of less than 1 milliseconds.

　　

Before starting this chapter, let's start by introducing the premium storage (premium Storage) Considerations:

1.Premium storage currently in azure China can only be created through PowerShell.

2.Premium Storage supported class Library: Storage REST API version 2014-02-14 or later; Service Management REST API version 2014-10-01 or later; Andazure PowerShell version 0.8.10 or later.

　　3.Premium storage currently only available in eastern China

4.Premium storage currently only supports page blobs and can only be used by VMS in the Azure DS family

The 5.Premium Storage only supports local redundancy (locally redundant Storage, LRS), which is a three-point redundancy of the same data center. For geo-redundancy when using premium storage, refer to: snapshot and copy Blob with premium storage

6. Non-DS series VMS (A-series VM,D series VMs) are not available with the premium Storage.

Only the DS family of VMs can use premium Storage. DS-Series VMs can use both premium Storage and standard Storage

7.Premium storage cannot be mapped to a custom domain name

8.Premium storage cannot be monitored using storage analytics. If monitoring is required, use operating system-based tools such as Windows Performance Monitor (for Windows VMS) and IOSTAT (for Linux VMs).

　

Important notes:

1. the maximum capacity of a single premium Storage account is 32TB. If you need to use the 40TB premium Storage, please use the two premium Storage account.

2. By default, the premium storage cache attached to the DS VM is set to read-write. This configuration setting is recommended for optimal application I/O performance. For frequently written or write-only disks (such as SQL Server log files), turn off the disk cache for better application performance.

3.Azure limits the network bandwidth of the DS VM to premium storage. For example, the STANDARD_DS1 VM provides dedicated bandwidth of up to MB per second for premium storage disk traffic. This means that the P10 premium storage disk attached to this VM can be up to a maximum of MB per second and not as high as the P10 disk by up to a maximum of two megabytes per second. Similarly, the Standard_ds13 VM can reach up to a maximum of one MB per second across all disks. Currently, the largest VM on the DS series is STANDARD_DS14, which can provide up to MB per second across all disks. Depending on the mixed form of read/write IO in disk communication, you may get a higher throughput than this value.

Note that these restrictions apply only to disk traffic. VM network traffic can use a separate bandwidth, which differs from the dedicated bandwidth of premium storage disks. The following table lists the current maximum IOPS and throughput (bandwidth) values for each DS series VM on all disks attached to the VM:

vm size	CPU	max iops	maximum disk bandwidth
standard_ds1	1	3,200	32mb/s
standard_ds2	2	6,400	64mb/s
standard_ds3	4	12,800	128mb/s
standard_ds4	8	25,600	256mb/s< /td>
standard_ds11	2	6,400	64mb/s
standard_ds12	4	12,800	128mb/s
standard_ds13	8	25,600	256mb/s
standard_ds14	/	50,000	512mb/s

4.DS-Series VMs can use both premium Storage and standard Storage

5. You can use storage Space to set up soft raid to increase the IOPS of the disk. For details, please refer to:

　　[New Portal] Windows Azure Virtual Machine (23) uses storage Space to increase the IOPS of Virtual machine disks

6. In case of system disk + data disk, if the system disk is only used for booting, consider using standard Storage, which can save cost. The data disk can use premium Storage because it performs better.

If the system disk and data disk have data transfer, the system disk can use premium storage for better performance.

　　

Advanced Storage Performance:

When you set up a disk for a premium storage account, the number of input/output operations (IOPS) and throughput (bandwidth) per second depends on the disk size. There are currently three types of premium storage disks: P10, P20, and P30. Each of these types has specific IOPS and throughput limits, as shown in the following table:

Premium Storage	P10	P20	P30
Disk size	128GB	512GB	1024GB
IOPS per disk	500	2300	5000
Throughput per disk	100mb/s	150mb/s	200mb/s

Azure maps the disk size (rounded up) to the closest premium storage disk option specified in the table. For example, a disk of size of three GB is categorized as the P10 option, which can execute up to 500 IO units per second and throughput of up to three megabytes per second. Similarly, disks with a size of three GB are categorized as P20 options, which can execute up to 2,300 IO units per second and throughput of up to four megabytes per second.

The input/output (I/O) unit size is zero KB. If the data to be transferred is less than the KB, it is treated as a single I/O unit. Larger I/O sizes are treated as multiple I/O with a size of up to KB. For example, 1100 KB of I/O is treated as five I/O units.

The throughput limit contains read and write disks. For example, the sum of reads and writes for a P10 disk should be less than or equal to about one MB per second. Similarly, a single P10 disk can have a read per second or a write throughput of one MB per second, or a read per second and a write throughput of up to MB per second.

When you create a disk in Azure, choose the most appropriate premium storage disk product based on your application's capacity, performance, scalability, and peak load requirements.

The following table describes the scalability goals for premium storage accounts:

Total account Capacity	Total bandwidth for locally redundant storage accounts
Disk Capacity: TB Snapshot capacity: Ten TB	Inbound + Outbound Highest per second

• Inbound refers to all data (requests) that are sent to the storage account.
• Outbound refers to all data (responses) received from the storage account.

　　How premium Storage is billed:

　　1.Premium Storage is billed as the maximum capacity allocated for the disk. For example, if you apply for a premium Storage of 1TB and you actually use only 1GB, Azure will be billed as the maximum capacity of the premium Storage, which is 1TB.

2.DS VMs are also billed in minutes. The price of the DS series VMS is the same as the price of the D-series VMs

============================= delimiter ===============================

The following are the key steps for using premium storage premium Storage and DS VMS:

1. Create Premium Storage

2. Create a DS VM

　　

1. First we run Azure PowerShell as an administrator

2. Select the current subscription:

Select-azuresubscription ' [Subscriptionname] ' –current

3. Create premium Storage in eastern China

" Yourpremiumaccount " " China East " " Premium_lrs "

　　

4. Create a new DS VM,VM size of DS2

$storageAccount="Yourpremiumaccount"$adminName="Youradmin"$adminPassword="YourPassword"$vmName="YOURVM"$location="China East"$imageName="A699494373c04fc0bc8f2bb1389d6106__windows-server-2012-r2-201409.01-en.us-127gb.vhd"$vmSize="Standard_ds2"$OSDiskPath="https://"+$storageAccount+". blob.core.chinacloudapi.cn/vhds/"+$vmName+"_os_pio.vhd"$VM= New-azurevmconfig-name$vmName-imagename$imageName-instancesize$vmSize-medialocation$OSDiskPathADD-azureprovisioningconfig-windows-vm$VM-adminusername$adminName-password$adminPasswordNew-azurevm-servicename$vmName-vms$VM-location$location

5. Mount the new data disk on the created DS VM:

$storageAccount="Yourpremiumaccount"$vmName="YOURVM"$VM= Get-azurevm-servicename$vmName-name$vmName$LunNo= 1$path="/ http"+$storageAccount+". blob.core.chinacloudapi.cn/vhds/"+"Mydatadisk_"+$LunNo+"_pio.vhd"$label="Disk"+$LunNoADD-azuredatadisk-createnew-medialocation$path-DISKSIZEINGB 128-disklabel$label-lun$LunNo-hostcaching READONLY-VM$VM| Update-azurevm

Resources:

https://azure.microsoft.com/en-us/documentation/articles/storage-premium-storage-preview-portal/

http://www.windowsazure.cn/documentation/articles/storage-premium-storage-preview-portal/?fb=001

　　

Windows Azure Virtual Machine (24) uses premium storage and DS series VMS