All Products
Search
Document Center

Elastic Compute Service:Classification and naming of instance types

Last Updated:Feb 27, 2026

Alibaba Cloud Elastic Compute Service (ECS) organizes instance types into families based on CPU architecture and target workload. This topic explains instance family categories, instance type naming conventions, and the metrics that define each instance type.

Instance family categories

ECS groups instance families into six categories: x86-based computing, Arm-based computing, ECS Bare Metal Instance, high-performance computing, Super Computing Cluster (SCC), and heterogeneous computing.

CategoryDescriptionProcessors
x86-based computingBased on the x86 architecture. Each virtual CPU (vCPU) corresponds to a hyperthread of a processor core. Includes enterprise-level and entry-level (shared) sub-categories.Intel, AMD, Hygon
Arm-based computingBased on the Arm architecture. Each vCPU corresponds to a physical processor core. Delivers stable performance using dedicated resources.YiTian 710, Ampere Altra
ECS Bare Metal InstanceCombines the strengths of physical machines and ECS instances using virtualization 2.0. Provides direct access to processor and memory resources without virtualization overhead. Retains hardware feature sets such as Intel VT-x and resource isolation capabilities.Varies by family
Super Computing Cluster (SCC)Built on ECS Bare Metal Instance with high-speed Remote Direct Memory Access (RDMA) interconnections for high-bandwidth, low-latency networking. Has all the benefits of ECS Bare Metal Instance.Varies by family
Heterogeneous computingIncludes Elastic GPU Service (GPU + CPU acceleration), video transcoding instance families, and visual computing instance families. The ebmgi6s visual computing family is based on the Alibaba Cloud SHENLONG architecture and Intel Server GPUs.GPUs, Field-Programmable Gate Arrays (FPGAs), Intel Server GPUs

Enterprise-level vs. shared instances

  • Enterprise-level instance families suit production workloads of all sizes, including databases, video encoding, and data analytics.

  • Shared instance families (entry-level) target small and medium-sized websites or individual developers. Shared instance types do not provide stable computing performance but cost less because they share underlying resources.

Arm-based use cases

Arm-based instance families suit containers, microservices, website and application servers, high-performance computing, and CPU-based machine learning.

Instance families and instance types

An instance family is a group of instance types that share the same processors and target similar workloads. Each instance family contains multiple instance types with different vCPU and memory configurations.

When you create an ECS instance, specify the instance type along with the network type, Elastic Block Storage (EBS) devices, and image.

For the full list of instance families and their specifications, see Overview of instance families.

Naming conventions

Each instance family name follows the format ecs.<Instance family>. Each instance type name follows the format ecs.<Instance family>.<Instance size>.

  • ecs -- the ECS product code.

  • &lt;Instance family&gt; -- consists of a name body and an optional suffix.

  • &lt;Instance size&gt; -- the number of vCPUs, separated from the instance family by a period.

The instance family name body contains:

  • Series letters (required) -- one or more lowercase letters indicating the workload category (for example, g for general-purpose).

  • Generation digit (required) -- indicates the instance family generation. Higher numbers represent newer, more cost-effective generations (for example, 8, 7, 6, 5).

  • Suffix letters (optional) -- one or more lowercase letters indicating processor type or additional capabilities (for example, ae for AMD-enhanced).

Instance size reference

The size label maps to vCPU count as follows:

Size labelvCPUsCalculation
small1--
large2--
xlarge41 x 4
2xlarge82 x 4
3xlarge123 x 4
4xlarge164 x 4
8xlarge328 x 4
16xlarge6416 x 4
32xlarge12832 x 4

Worked examples

The following examples show how to decode common instance type names.

Example 1: general-purpose, AMD-enhanced

ecs.g8ae.4xlarge

ComponentValueMeaning
ecsProduct codeECS
gSeriesGeneral-purpose (vCPU-to-memory ratio 1:4)
8Generation8th generation
aeSuffixAMD-enhanced processors
4xlargeSize16 vCPUs (4 x 4)

This instance type has 16 vCPUs and 64 GiB of memory (16 x 4 = 64 GiB, based on the 1:4 ratio of general-purpose families).

Example 2: compute-optimized, Intel

ecs.c8i.2xlarge

ComponentValueMeaning
ecsProduct codeECS
cSeriesCompute-optimized (vCPU-to-memory ratio 1:2)
8Generation8th generation
iSuffixIntel processors
2xlargeSize8 vCPUs (2 x 4)

Example 3: memory-optimized

ecs.r7.xlarge

ComponentValueMeaning
ecsProduct codeECS
rSeriesMemory-optimized (vCPU-to-memory ratio 1:8)
7Generation7th generation
*(none)*SuffixNo suffix (default processor)
xlargeSize4 vCPUs (1 x 4)

Example 4: Arm-based, YiTian

ecs.g8y.2xlarge

ComponentValueMeaning
ecsProduct codeECS
gSeriesGeneral-purpose (vCPU-to-memory ratio 1:4)
8Generation8th generation
ySuffixYiTian 710 Arm processors
2xlargeSize8 vCPUs (2 x 4)

Example 5: GPU-accelerated Bare Metal

ecs.ebmgn7ix.32xlarge

ComponentValueMeaning
ecsProduct codeECS
ebmPrefixECS Bare Metal Instance
gnSeriesNVIDIA GPU-accelerated compute-optimized
7Generation7th generation (Ampere architecture)
ixSuffixInference-optimized, with A10 GPUs (24 GB memory each), enhanced AMD CPUs
32xlargeSize128 vCPUs (32 x 4)

Example 6: GPU instance with vCPU-to-GPU ratio suffix

ecs.gn7i-c8g1.2xlarge

ComponentValueMeaning
ecsProduct codeECS
gn7iInstance familyNVIDIA GPU-accelerated, 7th gen, inference-optimized (A10)
-c8g1Ratio suffixvCPU-to-GPU ratio of 8:1 (c = cores/vCPUs, g = GPUs)
2xlargeSize8 vCPUs (2 x 4)

Example 7: economy instance with vCPU-to-memory ratio suffix

ecs.e-c1m4.xlarge

ComponentValueMeaning
ecsProduct codeECS
eSeriesEconomy
-c1m4Ratio suffixvCPU-to-memory ratio of 1:4 (c = cores/vCPUs, m = memory)
xlargeSize4 vCPUs (1 x 4)

Series reference for x86 and Arm instance families

The series letter indicates the workload category and defines the vCPU-to-memory ratio:

SeriesCategoryvCPU-to-memory ratioSuitable for
cCompute-optimized1:2Databases, web servers, high-performance scientific computing, game servers, batch computing, video encoding, machine learning
gGeneral-purpose1:4General-purpose applications, databases, websites, Java services, game servers
uUniversal1:1, 1:2, 1:4, 1:8Price-sensitive enterprise workloads, small to large applications, caches, search clusters
rMemory-optimized1:8 (most families)In-memory databases, data analytics, distributed caches (Redis), big data (Kafka, Elasticsearch)
reMemory-enhanced / high memoryVariesWorkloads requiring very high memory-to-vCPU ratios
hf, hc, hg, hrHigh clock speed1:2, 1:4, 1:8MMO games, high-performance scientific computing, large database systems
iLocal SSD-equipped1:4, 1:8Online transaction processing (OLTP), NoSQL databases (Cassandra, MongoDB), Elasticsearch, E-MapReduce
dBig data1:4 (most families)Hadoop MapReduce, Hadoop Distributed File System (HDFS), Hive, HBase, Kafka
sSharedVariesSmall and medium-sized websites, individual developers
tBurstableVariesIntermittent workloads with baseline + burst capacity
eEconomyVariesCost-sensitive workloads

Suffix reference

Suffixes fall into three categories: processor type, feature enhancement, and role specification.

Processor suffixes

SuffixMeaning
yIn-house Arm-based YiTian 710 processors
aAMD processors
aeAMD-enhanced processors
iIntel processors
hHygon processors

Feature suffixes

SuffixMeaning
reRDMA-enhanced
seStorage-enhanced
ne, nexNetwork-enhanced
tSecurity-enhanced
pPersistent memory-optimized

Role suffixes

SuffixMeaning
gGeneral-purpose
rMemory-optimized
cCompute-intensive

Series reference for heterogeneous, Bare Metal, and SCC instance families

These instance families use additional series prefixes:

Heterogeneous computing series

SeriesCategory
gnNVIDIA GPU-accelerated compute-optimized
vgnNVIDIA GRID vGPU-accelerated dedicated
sgnNVIDIA GRID vGPU-accelerated shared
giIntel GPU-accelerated compute-optimized
fFPGA-accelerated compute-optimized

Bare Metal and SCC series

SeriesCategory
ebmc, ebmg, ebmr, ebmgn, ebmhfECS Bare Metal Instance
sccc, sccg, scch, sccgn, scchfSuper Computing Cluster (SCC)

GPU generation and model suffixes

For GPU-accelerated instance families, the digit indicates the GPU architecture, and the suffix letter identifies the GPU model:

SuffixArchitectureGPU modelMemory per GPU
6vVolta or TuringNVIDIA V10016 GB
6eVolta or TuringNVIDIA V100 (second-generation, extended memory)32 GB
6iVolta or TuringNVIDIA T4--
6sVolta or TuringIntel Server GPU (sixth-generation SG1)--
7AmpereVaries--
7iAmpereNVIDIA A1024 GB
7eAmpereHigh-memory version of the same GPU model--
7sAmpereNVIDIA A30 (seventh-generation)--
The digit in the suffix (6 or 7) indicates the GPU architecture. The suffix letter identifies the specific GPU model or variant within that architecture generation.

Instance type metrics

The following metrics appear in instance type specification tables.

Processor

The physical CPU model powering the instance.

  • Base frequency -- the standard clock speed at which the processor runs under typical workloads, without overclocking or special optimization.

  • Turbo frequency -- the maximum clock speed the processor can temporarily achieve when demand increases.

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. Enterprise-level instance types in both architectures deliver stable performance using dedicated resources.

Burst performance (burstable instances only)

  • Average baseline CPU performance -- the CPU capacity continuously available to the instance.

  • CPU credits per hour -- the rate at which the instance earns CPU credits. The credits-per-hour value in instance type tables reflects the total credits earned by all vCPUs on the instance.

  • Maximum CPU credit balance -- the maximum credits the instance can accumulate within a 24-hour period. CPU credits are valid for up to 24 hours.

Memory

  • Memory -- stores data for rapid access while the instance runs. Data in memory is lost when the instance shuts down or restarts.

  • Persistent memory -- can serve as memory or local storage. Listed separately in instance type tables for families that support it.

  • Encrypted memory -- provided through Intel Software Guard Extensions (SGX) technology.

Network bandwidth

  • Baseline bandwidth -- the maximum amount of data that can be transmitted over a network connection in a specific period of time. This is the initial bandwidth setting for the network connection.

  • Burst bandwidth -- the peak bandwidth the instance can temporarily reach by consuming network burst credits. Available on specific instance types in 6th-generation or later families. No SLA commitment.

  • Full-duplex bandwidth -- supported on 7th-generation or later families. Inbound and outbound bandwidth each reach their specified values independently, without affecting each other.

All network specifications are measured in a forwarding-only test environment. Actual performance varies based on workload type, packet size, connection type (persistent or short-lived), image version, and networking model. Run stress tests on your actual workload to validate instance type selection.

Packet forwarding rate (PPS)

The sum of maximum inbound and outbound packet forwarding rates, measured in packets per second (PPS).

Measured in a forwarding-only test environment. Actual performance may vary.

Connections

A connection (session) is defined by a 5-tuple: source IP address, destination IP address, source port, destination port, and transport protocol. ECS connection metrics include TCP, UDP, and Internet Control Message Protocol (ICMP) connections.

NIC queues

The maximum number of network interface controller (NIC) queues supported per Elastic Network Interface (ENI). More NIC queues enable more efficient distribution of network traffic, reducing packet wait times, packet loss, and latency.

Elastic Network Interfaces (ENIs)

The maximum number of ENIs that can be bound to an instance. Bind secondary ENIs to different instances for flexible, scalable network configurations.

Elastic RDMA Interfaces (ERIs)

The maximum number of Elastic RDMA Interfaces (ERIs) that can be bound to an instance. ERIs are RDMA-capable ENIs that reuse the networks to which ENIs belong.

Jumbo frames support

Indicates whether the instance type supports Jumbo Frames. Alibaba Cloud supports jumbo frames with an 8,500-byte Ethernet payload.

Private IPv4 addresses per ENI

The maximum number of private IPv4 addresses supported per ENI.

IPv6 addresses per ENI

The maximum number of IPv6 addresses supported per ENI.

I/O optimization

I/O optimization provides improved network and storage performance for instances and cloud disks.

Local storage

Local storage (local disks) refers to disks attached to the physical machine hosting the ECS instance. Local storage provides temporary block storage, cannot be separately created, and is measured in GiB.

Warning

Local disks are subject to single point of failure (SPOF) risks. The durability of locally stored data depends on the reliability of the physical machine. Do not store persistent business data on local disks.

Disk bandwidth

  • Baseline disk bandwidth -- the sustained disk bandwidth guaranteed by the SLA for cloud disks.

  • Burst disk bandwidth -- the peak disk bandwidth the instance can temporarily reach. No SLA commitment.

Disk input/output operations per second (IOPS)

  • Baseline IOPS -- the sustained IOPS guaranteed by the SLA for cloud disks.

  • Burst IOPS -- the peak IOPS the instance can temporarily reach. No SLA commitment.

vTPM

Virtual Trusted Platform Module (vTPM) enables trusted computing capabilities. Trusted Platform Modules (TPMs) or Trusted Cryptography Modules (TCMs) on the underlying physical servers serve as trusted computing bases (TCBs), providing tamper-protected, trusted boot for instances. vTPM can be used to measure the critical components of the boot chain of instances.