Updated on 2025-11-14 GMT+08:00

x86-based Instance Specifications

TaurusDB for PostgreSQL supports the following x86-based instance specifications for the cloud SSD storage type: general-purpose (recommended) and dedicated (recommended). For details, see Table 1 and Table 2.

Table 1 x86-based instance specifications

Instance Specifications

Description

Scenario

Constraints

General-purpose (recommended)

CPU resources are shared with other general-purpose DB instances on the same physical machine. CPU usage is maximized through resource overcommitment. It is a cost-effective option and suitable for scenarios where stable performance is not critical.

Suitable for scenarios that have high requirements on cost-effectiveness.

These instance specifications are available in the following regions:

  • AP-Singapore
  • AP-Bangkok
  • TR-Istanbul
  • LA-Sao Paulo1
  • ME-Riyadh

Dedicated (recommended)

Your instance gets dedicated vCPUs and memory, so the performance is stable. It is not affected by other instances on the same physical machine. Dedicated instances are good for scenarios that require stable performance.

Suitable for core database scenarios such as e-commerce, gaming, finance, government, and enterprise applications.

Details of General-Purpose and Dedicated Instance Specifications

Table 2 Details of general-purpose and dedicated instance specifications

Instance Specifications

Specification Code for Primary/Standby Instances

Specification Code for Single-Node Instances

vCPUs

Memory (GB)

General-purpose

taurus.pg.n1.large.2.ha

taurus.pg.n1.large.2

2

4

taurus.pg.n1.large.4.ha

taurus.pg.n1.large.4

2

8

taurus.pg.n1.xlarge.2.ha

taurus.pg.n1.xlarge.2

4

8

taurus.pg.n1.xlarge.4.ha

taurus.pg.n1.xlarge.4

4

16

taurus.pg.n1.2xlarge.2.ha

taurus.pg.n1.2xlarge.2

8

16

taurus.pg.n1.2xlarge.4.ha

taurus.pg.n1.2xlarge.4

8

32

Dedicated

NOTE:

The specifications supported for cloud SSDs and extreme SSDs are different.

taurus.pg.x1.large.2.ha

-

2

4

taurus.pg.x1.large.4.ha

-

2

8

taurus.pg.x1.large.8.ha

-

2

16

taurus.pg.x1.xlarge.2.ha

-

4

8

taurus.pg.x1.xlarge.4.ha

-

4

16

taurus.pg.x1.xlarge.8.ha

taurus.pg.x1.xlarge.8

4

32

taurus.pg.x1.2xlarge.2.ha

taurus.pg.x1.2xlarge.2

8

16

taurus.pg.x1.2xlarge.4.ha

taurus.pg.x1.2xlarge.4

8

32

taurus.pg.x1.2xlarge.8.ha

taurus.pg.x1.2xlarge.8

8

64

taurus.pg.x1.4xlarge.2.ha

taurus.pg.x1.4xlarge.2

16

32

taurus.pg.x1.4xlarge.4.ha

taurus.pg.x1.4xlarge.4

16

64

taurus.pg.x1.4xlarge.8.ha

taurus.pg.x1.4xlarge.8

16

128

taurus.pg.x1.8xlarge.2.ha

taurus.pg.x1.8xlarge.2

32

64

taurus.pg.x1.8xlarge.4.ha

taurus.pg.x1.8xlarge.4

32

128

taurus.pg.x1.8xlarge.8.ha

taurus.pg.x1.8xlarge.8

32

256

taurus.pg.x1.16xlarge.2.ha

taurus.pg.x1.16xlarge.2

64

128

taurus.pg.x1.16xlarge.4.ha

taurus.pg.x1.16xlarge.4

64

256

taurus.pg.x1.16xlarge.8.ha

taurus.pg.x1.16xlarge.8

64

512

taurus.pg.x1.24xlarge.2.ha

taurus.pg.x1.24xlarge.2

96

192

taurus.pg.x1.24xlarge.4.ha

taurus.pg.x1.24xlarge.4

96

384

taurus.pg.x1.24xlarge.8.ha

taurus.pg.x1.24xlarge.8

96

768

taurus.pg.x1.32xlarge.2.ha

taurus.pg.x1.32xlarge.2

128

256

taurus.pg.x1.32xlarge.4.ha

taurus.pg.x1.32xlarge.4

128

512

taurus.pg.x1.32xlarge.8.ha

taurus.pg.x1.32xlarge.8

128

1,024

The DB instance specifications vary according to site requirements.