| What are you doing? | Consider these sizes |
|---|---|
| General use computing / web Testing and development, small to medium databases, or low to medium traffic web servers. | B, Dsv3, Dv3, DSv2, Dv2 |
| Heavy computational tasks Medium traffic web servers, network appliances, batch processes, and application servers. | Fsv2, Fs, F |
| Large memory usage Relational database servers, medium to large caches, and in-memory analytics. | Esv3, Ev3, M, GS, G, DSv2, Dv2 |
| Data storage and processing Big Data, SQL, and NoSQL databases, which need high disk throughput and IO. | Ls |
| Heavy graphics rendering or video editing, as well as model training and inferencing (ND) with deep learning. | NV, NC, NCv2, NCv3, ND |
| High-performance computing (HPC) If you need the fastest and most powerful CPU virtual machines with optional high-throughput network interfaces. | H |
storage options: traditional platter-based hard disk drive (HDD) or a more modern solid-state drive (SSD). There are two levels of SSD storage available: standard and premium. Choose Standard SSD disks if you have normal workloads but want better performance. Choose Premium SSD disks if you have I/O intensive workloads or mission-critical systems that need to process data very quickly.
unmanaged or managed disks
With unmanaged disks, you are responsible for the storage accounts that are used to hold the VHDs that correspond to your VM disks. You pay the storage account rates for the amount of space you use.A single storage account has a fixed rate limit of 20,000 I/O operations/sec. This means that a single storage account is capable of supporting 40 standard virtual hard disks at full throttle. If you need to scale out, then you need more than one storage account, which can get complicated.
Managed disks are the newer and recommended disk storage model. They elegantly solve this complexity by putting the burden of managing the storage accounts onto Azure.
No comments:
Post a Comment