This topic describes the local SSD-equiped instance type families i2, i2g, and i1, and lists the specific instance types within each of the instance type families.

i2, type family with local SSD disks

Features

  • I/O-optimized
  • Supports SSD Cloud Disks and Ultra Disks
  • High-performance local NVMe SSD disks with high IOPS, high I/O throughput, and low latency.
  • Equipped with a vCPU to memory ratio of 1:8, designed for high-performance databases
  • Equipped with 2.5 GHz Intel Xeon Platinum 8163 (Skylake) processors
  • Supports strong network performance through sufficient computing capacity
  • Suitable for the following scenarios:
    • OLTP and high-performance relational databases
    • NoSQL databases, such as Cassandra and MongoDB
    • Search applications, such as Elasticsearch

Instance types

Instance type  vCPU Memory (GiB)  Local disks (GiB)* Bandwidth (Gbit/s)**  Packet forwarding rate (Thousand pps)*** NIC queues**** ENIs*****
ecs.i2.xlarge 4 32.0 1 * 894 1.0 500 2 3
ecs.i2.2xlarge 8 64.0 1 * 1788 2.0 1,000 2 4
ecs.i2.4xlarge 16 128.0 2 * 1788 3.0 1,500 4 8
ecs.i2.8xlarge 32 256.0 4 * 1788 6.0 2,000 8 8
ecs.i2.16xlarge 64 512.0 8 * 1788 10.0 4,000 16 8

See other instance type families.

i2g, type family with local SSD disks

Features

  • I/O-optimized
  • Supports SSD Cloud Disks and Ultra Disks
  • High-performance local NVMe SSD disks with high IOPS, high I/O throughput, and low latency.
  • Equipped with a vCPU to memory ratio of 1:4, designed for high-performance databases
  • Equipped with 2.5 GHz Intel Xeon Platinum 8163 (Skylake) processors
  • Supports strong network performance through sufficient computing capacity
  • Suitable for the following scenarios:
    • OLTP and high-performance relational databases
    • NoSQL databases, such as Cassandra and MongoDB
    • Search applications, such as Elasticsearch

Instance types

Instance type  vCPU Memory (GiB)  Local disks (GiB)* Bandwidth (Gbit/s)**  Packet forwarding rate (Thousand pps)*** NIC queues**** ENIs*****
ecs.i2g.2xlarge 8 32.0 1 * 894 2.0 1,000 2 4
ecs.i2g.4xlarge 16 64.0 1 * 1788 3.0 1,500 4 8
ecs.i2g.8xlarge 32 128.0 2 * 1788 6.0 2,000 8 8
ecs.i2g.16xlarge 64 256.0 4 * 1788 10.0 4,000 16 8

See other instance type families.

i1, type family with local SSD disks

Features

  • I/O-optimized
  • Supports SSD Cloud Disks and Ultra Disks
  • High-performance local NVMe SSD disks with high IOPS, high I/O throughput, and low latency
  • Equipped with a vCPU to memory ratio of 1:4, designed for big data scenarios
  • Equipped with 2.5 GHz Intel Xeon E5-2682 v4 (Broadwell) processors
  • Supports strong network performance through sufficient computing capacity
  • Suitable for the following scenarios:
    • OLTP and high-performance relational databases
    • NoSQL databases, such as Cassandra and MongoDB
    • Search applications, such as Elasticsearch

Instance types

Instance type  vCPU Memory (GiB)  Local disks (GiB)* Bandwidth (Gbit/s)**  Packet forwarding rate (Thousand pps)*** NIC queues**** ENIs*****
ecs.i1.xlarge 4 16.0 2 * 104 0.8 200 1 3
ecs.i1.2xlarge 8 32.0 2 * 208 1.5 400 1 4
ecs.i1.3xlarge 12 48.0 2 * 312 2.0 400 1 6
ecs.i1.4xlarge 16 64.0 2 * 416 3.0 500 2 8
ecs.i1-c5d1.4xlarge 16 64.0 2 * 1456 3.0 400 2 8
ecs.i1.6xlarge 24 96.0 2 * 624 4.5 600 2 8
ecs.i1.8xlarge 32 128.0 2 * 832 6.0 800 3 8
ecs.i1-c10d1.8xlarge 32 128.0 2 * 1456 6.0 800 3 8
ecs.i1.14xlarge 56 224.0 2 * 1456 10.0 1,200 4 8

See other instance type families.

Characteristics and issues to note of i1

i1 is an I/O-optimized instance type family with local SSD disks, and is designed for scenarios that require high storage I/O performance. It is ideal for enterprises that provide online services, such as Internet games, e-commerce, live webcast, and Internet media, fully meeting the requirements for low latency and high I/O performance imposed by I/O-intensive applications. i1 can be used for businesses that require high storage I/O performance and have a high-availability architecture at the application layer, such as NoSQL non-relational databases, MPP data stores, and distributed file systems.

i1 has the following characteristics:

  • For large database applications, it offers tens of thousands of or even hundreds of thousands of low-latency random I/O reads and writes per second.
  • For large data set applications such as big data and parallel computing, it offers the sequential read and write throughput of up to several GiBs.
  • Based on local NVMe SSD disks, it provides up to hundreds of thousands of random I/O reads and writes while keeping a latency of μs.

When you use i1 instances, note the following:

  • i1 does not support changing configurations or downtime migration currently. Please check the official website notice regularly for the availability of these features.
  • Snapshots are not supported for local disks currently. Therefore, if you need to create a full image for an i1 instance, we recommend that you create it by combining the system disk snapshot and data disk (cloud disks only) snapshots. Currently you cannot create a full image based on an instance ID.
  • i1 instances are designed for scenarios that require high storage I/O performance. Local disks are attached to specific instance types and cannot be purchased separately. You cannot detach a local disk and then attach it to another instance.
  • The data disks of i1 instances are local disks that are subject to data loss (such as when NVMe SSD disks are faulty or the host is down). If your application cannot implement the data reliability architecture, we strongly recommend that you use cloud disks for your instances.
  • The following table shows how the operations on instances with local disks impact the disk data.
    Operation Status of disk data Description
    Restart the OS/restart an instance in the console/force restart an instance Retained Local disk volumes and data are retained.
    Shut down the OS/stop an instance in the console/force stop an instance Retained Local disk volumes and data are retained.
    Release an instance in the console Erased Local disk volumes and data are erased.
  • Do not use local disks to store business data that needs to be stored for a long time. Back up your data in a timely manner and adopt a high-availability architecture. For long-term storage of business data, cloud disks are recommended.
  • In VPCs, if an i1 instance had overdue payment or was stopped upon expiration before March 1st, 2018, its local disks were retained for 15 days. After March 1st, 2018, if an i1 instance has overdue payment or is stopped upon expiration, its local disks are released along with vCPUs and memory in 15 days.