This topic provides an overview of instance types for primary ApsaraDB RDS for PostgreSQL instances. The overview includes the most recent instance types, the phased-out instance types, and the specifications for each instance type.
For RDS instances that use cloud disks, the memory includes the memory that is occupied by the underlying operating system and the memory that is occupied by the RDS-related management services. Therefore, the available memory of an RDS instance may be less than the memory capacity that is supported by the instance type. The following list describes the memory that is occupied by the underlying operating system and the memory that is occupied by the RDS-related management services:
The underlying operating system occupies 500 MB to 700 MB of memory.
The RDS-related management services occupy approximately 500 MB of memory.
RDS instances that use cloud disks support only the virtual private cloud (VPC) network type. If you create an RDS instance that uses cloud disks in the ApsaraDB RDS console, you must set the Network Type parameter to VPC. If you create an RDS instance that uses cloud disks by calling an operation, you must set the InstanceNetworkType parameter to VPC. For more information, see Create an instance.
Instance types
If an RDS instance uses cloud disks and a dedicated instance type, the maximum IOPS of the instance is calculated by using the following formula:
Actual maximum IOPS = min{Maximum IOPS, IOPS that corresponds to the maximum I/O bandwidth, Cloud disk IOPS}.The size of an I/O operation in ApsaraDB RDS for PostgreSQL is 8 KB. IOPS that corresponds to the maximum I/O bandwidth is calculated by using the following formula:
IOPS that corresponds to the maximum I/O bandwidth = Maximum I/O bandwidth in MB/s × 1024/8.For more information about how to calculate the cloud disk IOPS, see IOPS.
The maximum IOPS and maximum I/O bandwidth cannot be guaranteed for RDS instances that use cloud disks and general-purpose instance types.
For more information about the differences between standard and YiTian product types, see Product types.
RDS instances that run RDS Basic Edition
Instance types for standard RDS instances
Instance family | Instance type | Number of CPU cores and memory capacity | Maximum number of connections | Maximum IOPS | Maximum I/O bandwidth (Unit: MB/s) | Storage capacity |
General-purpose instance family | pg.n2.2c.1m | 2 cores, 4 GB | 400 | The maximum IOPS and maximum I/O bandwidth cannot be guaranteed. If your workloads are sensitive to IOPS, we recommend that you use dedicated instance types. |
| |
pg.n4.2c.1m | 2 cores, 8 GB | 800 | ||||
pg.n2.4c.1m | 4 cores, 8 GB | 800 | ||||
pg.n4.4c.1m | 4 cores, 16 GB | 1,600 | ||||
pg.n4.6c.1m | 6 cores, 24 GB | 2,400 | ||||
pg.n4.8c.1m | 8 cores, 32 GB | 3,200 | ||||
Dedicated instance family | pg.x8.medium.1 | 2 cores, 16 GB | 1,600 | 10,000 | 128 | |
pg.x8.large.1 | 4 cores, 32 GB | 3,200 | 20,000 | 192 | ||
pg.x8.xlarge.1 | 8 cores, 64 GB | 6,400 | 25,000 | 256 | ||
pg.x4.2xlarge.1 | 16 cores, 64 GB | 6,400 | 40,000 | 384 | ||
pg.x8.2xlarge.1 | 16 cores, 128 GB | 12,800 | 40,000 | 384 | ||
pg.x4.4xlarge.1 | 32 cores, 128 GB | 12,800 | 60000 | 640 | ||
pg.x8.4xlarge.1 | 32 cores, 256 GB | 25,600 | 60000 | 640 | ||
Instance types for YiTian RDS instances
If you want to purchase an instance type that is available for an YiTian RDS instance, the RDS instance must meet the following requirements:
The RDS instance uses the subscription billing method.
The RDS instance runs PostgreSQL 13 or later.
The RDS instance uses Enterprise SSDs (ESSDs) or general ESSDs.
The RDS instance resides in a zone of one of the following regions: China (Hangzhou), China (Shanghai), China (Beijing), China (Zhangjiakou), China (Shenzhen), and Singapore.
NoteInstance types for YiTian RDS instances are available in a few regions and will be available in other regions and zones in phases. For more information about the regions, visit the ApsaraDB RDS buy page.
Instance family | Instance type | Number of CPU cores and memory capacity | Maximum number of connections | Maximum IOPS | Maximum I/O bandwidth (Unit: MB/s) | Storage capacity |
General-purpose instance family | pg.n1e.2c.1m | 2 cores, 2 GB | 200 | The maximum IOPS and maximum I/O bandwidth cannot be guaranteed. If your workloads are sensitive to IOPS, we recommend that you use dedicated instance types for standard RDS instances on RDS Basic Edition or dedicated instance types for YiTian RDS instances on RDS High-availability Edition. |
| |
pg.n2e.2c.1m | 2 cores, 4 GB | 400 | ||||
RDS instances that run RDS High-availability Edition
Instance types for standard RDS instances
Instance types for YiTian RDS instances
If you want to purchase an instance type that is available for an YiTian RDS instance, the RDS instance must meet the following requirements:
The RDS instance runs PostgreSQL 13 or later.
The RDS instance uses PL1 ESSDs, PL2 ESSDs, or PL3 ESSDs.
The RDS instance resides in one of the following regions: China (Hangzhou), China (Shanghai), China (Beijing), China (Zhangjiakou), China (Shenzhen), and Singapore.
NoteInstance types for YiTian RDS instances are available in a few regions and will be available in other regions and zones in phases. For more information about the regions, visit the ApsaraDB RDS buy page.
Usage notes
Instance types for the YiTian product type are not supported for RDS instances for which Babelfish is enabled. For more information, see Introduction to Babelfish.
You can change the instance type of an RDS instance from an instance type for the standard product type to an instance type for the YiTian product type. For more information, see Change instance specifications.
Instance types
RDS edition | Instance family | Instance type | Number of CPU cores and memory capacity | Maximum number of connections | Maximum IOPS | Maximum I/O bandwidth (Unit: MB/s) | Storage capacity |
RDS High-availability Edition | General-purpose instance family | pg.n4m.2c.2m | 2 cores, 8 GB | 800 | The maximum IOPS and maximum I/O bandwidth cannot be guaranteed. If your workloads are sensitive to IOPS, we recommend that you use dedicated instance types. |
| |
pg.n4m.4c.2m | 4 cores, 16 GB | 1,600 | |||||
pg.n4m.8c.2m | 8 cores, 32 GB | 3,200 | |||||
pg.n2m.2c.2m | 2 cores, 4 GB | 400 | |||||
pg.n2m.4c.2m | 4 cores, 8 GB | 800 | |||||
pg.n2m.8c.2m | 8 cores, 16 GB | 1,600 | |||||
Dedicated instance family | pg.x2m.medium.2c | 2 cores, 4 GB | 400 | 20,000 | 192 | ||
pg.x4m.medium.2c | 2 cores, 8 GB | 800 | 20,000 | 192 | |||
pg.x8m.medium.2c | 2 cores, 16 GB | 1,600 | 20,000 | 192 | |||
pg.x2m.large.2c | 4 cores, 8 GB | 800 | 40,000 | 256 | |||
pg.x4m.large.2c | 4 cores, 16 GB | 1,600 | 40,000 | 256 | |||
pg.x8m.large.2c | 4 cores, 32 GB | 3,200 | 40,000 | 256 | |||
pg.x2m.xlarge.2c | 8 cores, 16 GB | 1,600 | 50,000 | 384 | |||
pg.x4m.xlarge.2c | 8 cores, 32 GB | 3,200 | 50,000 | 384 | |||
pg.x8m.xlarge.2c | 8 cores, 64 GB | 6,400 | 50,000 | 384 | |||
pg.x2m.2xlarge.2c | 16 cores, 32 GB | 3,200 | 80,000 | 640 | |||
pg.x4m.2xlarge.2c | 16 cores, 64 GB | 6,400 | 80,000 | 640 | |||
pg.x8m.2xlarge.2c | 16 cores, 128 GB | 12,800 | 80,000 | 640 | |||
pg.x2m.4xlarge.2c | 32 cores, 64 GB | 6,400 | 125,000 | 1,024 | |||
pg.x4m.4xlarge.2c | 32 cores, 128 GB | 12,800 | 125,000 | 1,024 | |||
pg.x8m.4xlarge.2c | 32 cores, 256 GB | 25,600 | 125,000 | 1,024 | |||
pg.x2m.8xlarge.2c | 64 cores, 128 GB | 12,800 | 240,000 | 2,048 | |||
pg.x4m.8xlarge.2c | 64 cores, 256 GB | 25,600 | 240,000 | 2,048 | |||
pg.x8m.8xlarge.2c | 64 cores, 512 GB | 51,200 | 240,000 | 2,048 | |||
RDS instances that run RDS Cluster Edition
Instance types for standard RDS instances
Instance types for YiTian RDS instances
If you want to purchase an instance type that is available for an YiTian RDS instance, the RDS instance must meet the following requirements:
The RDS instance runs PostgreSQL 14 or later.
The RDS instance uses PL1 ESSDs, PL2 ESSDs, or PL3 ESSDs.
The RDS instance resides in one of the following regions: China (Hangzhou), China (Shanghai), China (Beijing), China (Zhangjiakou), China (Shenzhen), and Singapore.
NoteInstance types for YiTian RDS instances are available in a few regions and will be available in other regions and zones in phases. For more information about the regions, visit the ApsaraDB RDS buy page.
Usage notes
Instance types for the YiTian product type are not supported for RDS instances for which Babelfish is enabled. For more information, see Introduction to Babelfish.
You can change the instance type of an RDS instance from an instance type for the standard product type to an instance type for the YiTian product type. For more information, see Change instance specifications.
Instance types
RDS edition | Instance family | Instance type | Number of CPU cores and memory capacity | Maximum number of connections | Maximum IOPS | Maximum I/O bandwidth (Unit: MB/s) | Storage capacity |
RDS Cluster Edition | General-purpose instance family | pg.n4e.2c.xc | 2 cores, 8 GB | 800 | The maximum IOPS and maximum I/O bandwidth cannot be guaranteed. If your workloads are sensitive to IOPS, we recommend that you use dedicated instance types. |
| |
pg.n4e.4c.xc | 4 cores, 16 GB | 1,600 | |||||
pg.n4e.8c.xc | 8 cores, 32 GB | 3,200 | |||||
pg.n2e.2c.xc | 2 cores, 4 GB | 400 | |||||
pg.n2e.4c.xc | 4 cores, 8 GB | 800 | |||||
pg.n2e.8c.xc | 8 cores, 16 GB | 1,600 | |||||
Dedicated instance family | pg.x2e.medium.xc | 2 cores, 4 GB | 400 | 20,000 | 192 | ||
pg.x4e.medium.xc | 2 cores, 8 GB | 800 | 20,000 | 192 | |||
pg.x8e.medium.xc | 2 cores, 16 GB | 1,600 | 20,000 | 192 | |||
pg.x2e.large.xc | 4 cores, 8 GB | 800 | 40,000 | 256 | |||
pg.x4e.large.xc | 4 cores, 16 GB | 1,600 | 40,000 | 256 | |||
pg.x8e.large.xc | 4 cores, 32 GB | 3,200 | 40,000 | 256 | |||
pg.x2e.xlarge.xc | 8 cores, 16 GB | 1,600 | 50,000 | 384 | |||
pg.x4e.xlarge.xc | 8 cores, 32 GB | 3,200 | 50,000 | 384 | |||
pg.x8e.xlarge.xc | 8 cores, 64 GB | 6,400 | 50,000 | 384 | |||
pg.x2e.2xlarge.xc | 16 cores, 32 GB | 3,200 | 80,000 | 640 | |||
pg.x4e.2xlarge.xc | 16 cores, 64 GB | 6,400 | 80,000 | 640 | |||
pg.x8e.2xlarge.xc | 16 cores, 128 GB | 12,800 | 80,000 | 640 | |||
pg.x2e.4xlarge.xc | 32 cores, 64 GB | 6,400 | 125,000 | 1,024 | |||
pg.x4e.4xlarge.xc | 32 cores, 128 GB | 12,800 | 125,000 | 1,024 | |||
pg.x8e.4xlarge.xc | 32 cores, 256 GB | 25,600 | 125,000 | 1,024 | |||
pg.x2e.8xlarge.xc | 64 cores, 128 GB | 12,800 | 240,000 | 2,048 | |||
pg.x4e.8xlarge.xc | 64 cores, 256 GB | 25,600 | 240,000 | 2,048 | |||
pg.x8e.8xlarge.xc | 64 cores, 512 GB | 51,200 | 240,000 | 2,048 | |||
Phased-out instance types
The following table describes the phased-out instance types of ApsaraDB RDS for PostgreSQL. The phased-out instance types are no longer available to new RDS instances. We recommend that you select available instance types for new RDS instances.