This topic provides an overview of instance types for YiTian primary ApsaraDB RDS for MySQL instances that originally use the ARM architecture. The overview includes the most recent instance types and the specifications for each instance type.
The YiTian product type is supported for RDS instances that run MySQL 8.0 and MySQL 5.7.
Instance types that are supported for YiTian RDS instances on RDS High-availability Edition or RDS Cluster Edition are available in the following regions: China (Hangzhou), China (Shanghai), China (Beijing), China (Zhangjiakou), China (Ulanqab), China (Shenzhen), China (Guangzhou), China (Chengdu), Indonesia (Jakarta), China (Hong Kong), and Singapore. The instance types will be available in other regions in phases. The ApsaraDB RDS buy page displays the regions that support the instance types.
For more information about the instance types that are supported for YiTian RDS instances on RDS Basic Edition, see Supported regions and billing methods.
The instance types vary based on the region of your RDS instance. The instance types that are displayed on the ApsaraDB RDS buy page shall prevail.
The maximum number of connections in this topic indicates the maximum number of processes that can be connected to the RDS instance at a time.
General-purpose instance types cannot ensure the maximum IOPS and maximum I/O bandwidth. For more information, see IOPS.
Instance types available for RDS Basic Edition
General-purpose instance types
Instance type | Number of CPU cores and memory capacity | Maximum number of connections |
mysql.n1e.small.1 (YiTian) | 1 core, 1 GB | 300 |
mysql.n2e.small.1 (YiTian) | 1 core, 2 GB | 600 |
mysql.n1e.medium.1 (YiTian) | 2 cores, 2 GB | 1,000 |
mysql.n2e.medium.1 (YiTian) | 2 cores, 4 GB | 2,000 |
Instance types available for RDS High-availability Edition
General-purpose instance types
Instance type | Number of CPU cores and memory capacity | Maximum number of connections | Storage capacity |
mysql.n2m.small.2c | 1 core, 2 GB | 2,000 |
|
mysql.n2m.medium.2c | 2 cores, 4 GB | 4,000 | |
mysql.n4m.medium.2c | 2 cores, 8 GB | 6,000 | |
mysql.n8m.medium.2c | 2 cores, 16 GB | 8,000 | |
mysql.n2m.large.2c | 4 cores, 8 GB | 6,000 | |
mysql.n4m.large.2c | 4 cores, 16 GB | 8,000 | |
mysql.n8m.large.2c | 4 cores, 32 GB | 12,000 | |
mysql.n2m.xlarge.2c | 8 cores, 16 GB | 8,000 | |
mysql.n4m.xlarge.2c | 8 cores, 32 GB | 10,000 | |
mysql.n8m.xlarge.2c | 8 cores, 64 GB | 16,000 |
Dedicated instance types
Instance type | Number of CPU cores and memory capacity | Maximum number of connections | Maximum IOPS | Maximum I/O Bandwidth (Mbit/s) | Storage capacity |
mysql.x4m.medium.2c | 2 cores, 8 GB | 6,000 | 10,000 | 1,024 |
|
mysql.x8m.medium.2c | 2 cores, 16 GB | 8,000 | 10,000 | 1,024 | |
mysql.x2m.large.2c | 4 cores, 8 GB | 6,000 | 40,000 | 2,048 | |
mysql.x4m.large.2c | 4 cores, 16 GB | 8,000 | 40,000 | 2,048 | |
mysql.x8m.large.2c | 4 cores, 32 GB | 12,000 | 40,000 | 2,048 | |
mysql.x2m.xlarge.2c | 8 cores, 16 GB | 8,000 | 50,000 | 3,072 | |
mysql.x4m.xlarge.2c | 8 cores, 32 GB | 10,000 | 50,000 | 3,072 | |
mysql.x8m.xlarge.2c | 8 cores, 64 GB | 16,000 | 50,000 | 3,072 | |
mysql.x2m.2xlarge.2c | 16 cores, 32 GB | 16,000 | 80,000 | 5,120 | |
mysql.x4m.2xlarge.2c | 16 cores, 64 GB | 20,000 | 80,000 | 5,120 | |
mysql.x8m.2xlarge.2c | 16 cores, 128 GB | 32,000 | 80,000 | 5,120 | |
mysql.x2m.4xlarge.2c | 32 cores, 64 GB | 32,000 | 125,000 | 8,192 | |
mysql.x4m.4xlarge.2c | 32 cores, 128 GB | 40,000 | 125,000 | 8,192 |