Alibaba Cloud provides various instance types to fit different use cases. This topic describes the relationships between instance family categories, instance families, and instance types. This topic also describes the naming conventions of instance types.
Differences between instance family categories
Alibaba Cloud groups instance families into the following categories based on the CPU architecture and supported scenarios: x86-based computing, Arm-based computing, ECS Bare Metal Instance, High-performance computing, Super Computing Cluster (SCC), and heterogeneous computing.
Instance family category | Description |
x86-based computing and Arm-based computing instance family categories |
|
ECS Bare Metal Instance family category | ECS Bare Metal Instance combines the strengths of physical machines and ECS instances to deliver powerful and robust computing capabilities. ECS Bare Metal Instance uses virtualization 2.0 to provide your business applications with direct access to the processor and memory resources of the underlying servers without virtualization overheads. ECS Bare Metal Instance retains the hardware feature sets, such as Intel VT-x, and resource isolation capabilities of physical machines, which is ideal for applications that need to run in non-virtualization environments in the cloud. |
SCC instance family category | SCC is based on ECS Bare Metal Instance and uses high-speed Remote Direct Memory Access (RDMA)-based interconnections to significantly improve the network performance and acceleration ratio of large-scale clusters. SCC has all the benefits of ECS Bare Metal Instance and provides high-bandwidth, low-latency networks. |
Heterogeneous computing instance family category |
|
Relationships between instance families and instance types
An instance family is a group of instance types that use the same processors and are suitable for similar business and use scenarios. Each instance family consists of multiple instance types that each have a combination of different capacities, including CPU and memory capacities. The ECS instance type defines the basic properties of an ECS instance, including CPU (CPU model and clock speed) and memory. When you create a instance, you must configure the instance type, network type, Elastic Block Storage (EBS) devices, and image.
The following figure shows the relationships between instance families and instance types.
Only specific instance families and types are shown in the figure. For information about the other instance families and instance types, see Overview of instance families.
Naming conventions of instance types
Each instance family name is in the ecs.<Instance family>
format. Each instance type name is in the ecs.<Instance family>.<Instance size>
format.
ecs
: the product code of ECS.<Instance family>
: consists of an instance family name body and an instance family name suffix.<Instance size>
: the number of vCPUs, which can besmall
,large
, or<nx>large
.small
indicates 1 vCPU,large
indicates 2 vCPUs, andxlarge
indicates 4 vCPUs. A larger value of n in <nx> indicates a larger number of vCPUs. For example,2xlarge
indicates 8 vCPUs (= 2 × 4) and3xlarge
indicates 12 vCPUs (= 3 × 4).
x86-based computing instance families and Arm-based computing instance families
For example, ecs.g8ae.4xlarge
is an instance type in a general-purpose instance family and is powered by enhanced AMD CPUs. The instance type has 16 vCPUs (= 4 × 4). The instance type has 64 GiB of memory based on the CPU-to-memory ratio of 1:4 of general-purpose instance families.
Instance type names vary in the <Instance family> part. The following table describes the <Instance family> part of each instance type name.
Instance family name body (lowercase letters + digits) | Instance family name suffix | |
Lowercase letter | Digit | Lowercase letter |
An abbreviation that indicates the performance characteristics of the instance family.
| The generation to which the instance family belongs. A larger number indicates a newer generation of instance families that is more cost-effective. Examples: 8, 7, 6, and 5. | An abbreviation that indicates the other characteristics of the instance family.
|
Heterogeneous computing instance families, ECS Bare Metal Instance families, and SCC instance families
For example, ecs.ebmgn7ix.32xlarge
is an instance type in a GPU-accelerated, compute-optimized ECS Bare Metal Instance family. The instance type is powered by NVIDIA A10 GPUs with 24 GB of memory each and enhanced AMD CPUs. The instance type has 128 vCPUs (= 32 × 4). The digit 7 indicates the Ampere architecture.
Instance type names vary in the <Instance family> part. The following table describes the <Instance family> part of each instance type name.
Instance family name body (lowercase letters) | Instance family name suffix (lowercase letters + digits) |
|
|
Instance type metrics
Metric | Description |
Processor | The physical CPU model of an ECS instance. The performance of the processor varies based on the processor type.
|
vCPU | Each vCPU of x86-based instance types corresponds to a hyperthread of a processor core. Each vCPU of Arm-based instance types corresponds to a physical processor core. The instance types deliver stable performance by using dedicated resources. |
Burst performance |
|
Memory |
|
Network bandwidth |
Note Instance type specifications are all verified and obtained in a pure forwarding test environment. In actual business scenarios, the performance of an ECS instance may vary based on other factors such as instance workload type, packet size, connection type (persistent or short-lived), image version, and networking model. We recommend that you perform business stress tests on instances to select appropriate instance types. |
Packet forwarding rate (pps) | The sum of maximum inbound and outbound packet forwarding rates. For information about how to test the packet forwarding rate of an ECS instance, see Test the network performance of an instance. Note Instance type specifications are all verified and obtained in a pure forwarding test environment. In actual business scenarios, the performance of an ECS instance may vary based on other factors such as instance workload type, packet size, connection type (persistent or short-lived), image version, and networking model. We recommend that you perform business stress tests on instances to select appropriate instance types. |
Connections | A connection, also called a session, is the process of connecting a client to a server and transferring data between the client and the server. A connection is uniquely defined by the network communication quintuple that consists of a source IP address, a destination IP address, a source port, a destination port, and a protocol. The connections of an ECS instance include TCP, UDP, and Internet Control Message Protocol (ICMP) connections. If your business is sensitive to concurrent network connections, select an instance of an instance type of which the maximum number of connections meets your business requirements. |
NIC queues | The maximum number of network interface controller (NIC) queues that is supported by the instance type per elastic network interface (ENI). It is also the maximum number of traffic queues that an instance can process on each ENI. A larger number of NIC queues indicates more efficient distribution and processing of network data, less time that packets wait to be processed, improved network performance, and lower packet loss rate and network latency. Specify a proper number of NIC queues based on the network workload, hardware performance, and system configurations. For more information, see Manage NIC multi-queue. |
ENIs | The maximum number of ENIs that can be bound to an instance. You can bind one or more ENIs to each ECS instance. You can bind secondary ENIs to or unbind secondary ENIs from different ECS instances to allow for more flexibility and scalability in network configurations and meet network requirements in different scenarios. For example, you can use ENIs to create multi-IP address, multi-NIC, or high-availability networks. For more information, see Overview. |
ERIs | The maximum number of elastic RDMA interfaces (ERIs) that can be bound to an instance. ERIs are Remote Direct Memory Access (RDMA)-capable ENIs. ERIs reuse the networks to which ENIs belong. This allows you to use the RDMA feature in the original networks and enjoy the low latency provided by RDMA without the need to modify service networking. For more information, see Overview. |
Support for Jumbo Frames | Specifies whether the instance type supports the Jumbo Frames feature. Alibaba Cloud supports jumbo frames that are 8,500 bytes in size and allows you to send Ethernet frames that have 8,500 bytes of payload. Jumbo frames increase the payload size per packet and the percentage of the packet that is not packet overhead to provide high throughput and high network performance. For information about how to enable the Jumbo Frames feature, see Jumbo frames. |
Private IPv4 addresses per ENI | The maximum number of private IPv4 addresses that is supported by the instance type per ENI. |
IPv6 addresses per ENI | The maximum number of IPv6 addresses that is supported by the instance type per ENI. |
I/O optimized | I/O optimization provides better network capabilities and storage performance for instances and cloud disks. For example, you can attach a standard SSD to an I/O optimized instance to maximize the storage performance of the standard SSD. |
Local storage | Local storage, also called local disks, refers to disks that are attached to the physical machines on which ECS instances are hosted. Local storage provides temporary block storage for ECS instances. Local storage cannot be separately created and is measured in a binary unit of GiB. Warning The durability of data stored in a local disk is determined by the reliability of the associated physical machine. Local disks are subject to single point of failure (SPOF) risks. Data stored on local disks may be lost. Do not store long-lived business data on local disks. For more information, see Local disks. |
Disk bandwidth |
|
Disk IOPS |
|
vTPM | Trusted computing capabilities: Trusted Platform Modules (TPMs) or Trusted Cryptography Modules (TCMs) serve as trusted computing bases (TCBs) on the underlying physical servers that host trusted instances to ensure the tamper-protected, trusted boot of the instances. Virtual TPM (vTPM) can be used to measure the critical components of the boot chain of instances. |