Description:

Elastic Volume Service (EVS) provides cloud servers with scalable block storage. EVS discs can be used for distributed file systems.

§  Development And Testing Environments

§  Data Warehouse Applications

§  High-Performance Computing (HPC) Scenarios

They are used to meet a variety of service requirements thanks to its high reliability, high performance, and extensive specifications. Elastic Cloud Servers (ECSs) and Bare Metal Servers are among the servers that EVS supports (BMSs).

EVS discs are similar to hard disc drives in personal computers. They can only be used in conjunction with servers and cannot be utilized on their own. EVS drives can be initialized, file systems created, and data stored persistently.

Architecture Of EVS:

In the Architecture diagram above we can clearly see the concept of EVS disk architecture which is quite simple, Multiple EVS disks can be directly attached to the Elastic cloud servers and bare metal servers. The EVs disk backup be created to ensure safety of saved data on these disks and at the same time the snapshots are also created to attain a particular image of the disk at a particular stage and new disks can also be initiated with the help of these backups and snapshots

Salient Features:

Some of the salient features of EVS are as follows

o   You can choose from a variety of EVS disc types, and EVS discs can be utilized as both data and system drive for servers. Depending on your budget and service requirements, you can choose the disc type.

o   The capacity of the EVS discs ranges from 10 GB to 32 TB. You can increase the disc storage up to 32 TB in 1 GB increments without disrupting your applications if it no longer satisfies your demands.

o   Data encryption is supported on both system and data drives to protect data security.

o   You can check the disc health and operation status at any moment with Cloud Eye.

How to choose EVS according to your requirement:

Before Choosing an EVS disk first we need to understand the metrics that define the EVS Performance so we can easily shortlist product in our required Category, so following Figure1 is an explanation of the metrics

Figure 1: Performance Metrics for EVS Disk Performance

Now step 2 is whether we need disk i/o performance then the following Figure 2 summarizes the EVS disks types based on Disk I/O performance

Figure2: EVS disks types based on Disk I/O performance

Now here I am going o describe in detail with the help of application scenarios so you can select it with your requirements

Extreme SSD:

First, we will see Extreme SSD as it is Suitable for scenarios like

·       Databases

·       Oracle

·       SQL Server

·       ClickHouse

·       AI scenarios

All the above scenarios require, Extremely high bandwidth and very low latency

So ESSD Provides

      i.            IOPS of 128,000

  ii.            Max. throughput 1,000 MB/s

iii.            Disk IOPS= Min. (128,000, 1800 + 50 x Capacity)

iv.            Single-queue access latency 200 μs

Ultra-high I/O:

Next is Ultra-high I/O SSD which is suitable for scenarios like

·       Read/write-intensive applications that require ultra-large bandwidth

·       Transcoding services

·       I/O-intensive applications

·       NoSQL

·       Oracle

·       SQL Server

·       PostgreSQL

·       Latency-sensitive applications

·       Redis

·       Memcache

It is suitable workloads demanding

high throughput and low latency

It Provides,

      i.            IOPS of 50,000

   ii.            Max. throughput 350 MB/s

iii.            Disk IOPS= Min. (50,000, 1800 + 50 x Capacity)

iv.            Single-queue access latency 1ms

General Purpose SSD

GPSSD Disks developed for enterprise office applications that require high throughput and low latency at a low cost. High-performance, low-latency interactive apps are becoming typical. Application scenarios are

·       Applications for business offices

·       Development and testing on a large scale

·       Services for transcoding

·       Logs from the web server

·       Container discs, for example, are high-performance system discs.

It Provides,

      i.            IOPS of 20,000

   ii.            Max. throughput 250 MB/s

iii.            Disk IOPS= Min. (20,000, 1800 + 50 x Capacity)

iv.            Single-queue access latency 1 ms

High I/O:

SAS Disks that are ideal for workloads that are often accessed such as,

·       Common development and testing

It Provides,

      i.            IOPS of 5,000

   ii.            Max. throughput 150 MB/s

iii.            Disk IOPS= Min. (5,000, 1800 + 50 x Capacity)

iv.            Single-queue access latency 1ms to 3ms

Common I/O (Previous Generation Product):

SATA Disks designed for workloads that aren't as frequently accessed. Large capacity, medium read/write speed, but few transactions are required by applications such as.

·       Typical office software

·       Testing and development of lightweight products

·       It is not advised that these discs be utilized as system discs.

It Provides,

      i.            IOPS of 2,200

   ii.            Max. throughput 50 MB/s

iii.            Disk IOPS= Min. (2,200, 1800 + 50 x Capacity)

iv.            Single-queue access latency 5ms to 10ms

Conclusion:

The total of read and write operations is used to compute maximum IOPS, maximum throughput, and burst IOPS limits. The value of the volume type argument in the EVS API is indicated by this API name. The kind of the underlying hardware device is not represented. Depending on which comes first, a large-capacity disc can attain either maximum IOPS or maximum throughput. The data block size has a direct impact on EVS disc performance. The disc can reach the maximum IOPS for small data blocks, such as 4 KB or 8 KB. The disc can reach its maximum performance for data blocks of a considerable size, more than or equal to 16 KB.

So one can choose accordingly  with there desired requirement provided the above detailed explanation of all the available types.