Help Center/ TaurusDB/ Service Overview/ Instance Description/ Instance Specifications
Updated on 2024-12-30 GMT+08:00
View PDF
Share

Instance Specifications

The CPU architecture of TaurusDB instances can be x86 or Kunpeng.

  • x86 instances use Intel® Xeon® Scalable processors and feature robust and stable computing performance. When working on high-performance networks, the instances provide the additional performance and stability that enterprise-class applications demand.
  • Kunpeng instances use Kunpeng 920 processors and 25GE high-speed intelligent NICs for powerful compute and high-performance networks, making them an excellent choice for enterprises needing cost-effective, secure, and reliable cloud services.

Different CPU architectures support different instance specifications. The details are as follows.

x86 Instance Specifications

x86 instances support both dedicated and general-purpose specifications.

  • Dedicated: CPU and memory resources are dedicated for use and performance is stable without being affected by other instances on the same physical machine. Dedicated instances are good for scenarios that require stable performance.

    Dedicated instances are available in following regions: CN North-Beijing4, CN East-Shanghai1, CN South-Guangzhou, CN South-Guangzhou-InvitationOnly, CN Southwest-Guiyang1, CN North-Ulanqab1, AP-Singapore, AP-Jakarta, TR-Istanbul, and LA-Sao Paulo1.

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

    General-purpose instances are available in following regions: CN North-Beijing4, CN East-Shanghai1, and CN South-Guangzhou.

Table 1 x86 instance specifications

Specifications

Specification Code

vCPUs

Memory (GB)

Dedicated

gaussdb.mysql.large.x86.4

2

8

gaussdb.mysql.large.x86.8

2

16

gaussdb.mysql.xlarge.x86.4

4

16

gaussdb.mysql.xlarge.x86.8

4

32

gaussdb.mysql.2xlarge.x86.4

8

32

gaussdb.mysql.2xlarge.x86.8

8

64

gaussdb.mysql.4xlarge.x86.4

16

64

gaussdb.mysql.4xlarge.x86.8

16

128

gaussdb.mysql.8xlarge.x86.4

32

128

gaussdb.mysql.8xlarge.x86.8

32

256

gaussdb.mysql.16xlarge.x86.4

60

256

gaussdb.mysql.16xlarge.x86.8

64

512

General-purpose

gaussdb.mysql.large.x86.normal.4

2

8

gaussdb.mysql.xlarge.x86.normal.2

4

8

gaussdb.mysql.xlarge.x86.normal.4

4

16

gaussdb.mysql.2xlarge.x86.normal.2

8

16

gaussdb.mysql.2xlarge.x86.normal.4

8

32

gaussdb.mysql.4xlarge.x86.normal.2

16

32

gaussdb.mysql.4xlarge.x86.normal.4

16

64

gaussdb.mysql.8xlarge.x86.normal.2

32

64

gaussdb.mysql.8xlarge.x86.normal.4

32

128
  • The DB instance specifications vary according to site requirements.
  • For information about Transactions Per Second (TPS) and Queries Per Second (QPS), see Performance White Paper.

Kunpeng Instance Specifications

Kunpeng instances only support dedicated specifications.

Dedicated: CPU and memory resources are dedicated for use and performance is stable without being affected by other instances on the same physical machine. Dedicated instances are good for scenarios that require stable performance.

Dedicated instances are available in following regions: CN North-Beijing4, CN East-Shanghai1, CN South-Guangzhou, CN South-Guangzhou-InvitationOnly, CN Southwest-Guiyang1, CN North-Ulanqab1, AP-Singapore, AP-Jakarta, TR-Istanbul, and LA-Sao Paulo1.

Table 2 Kunpeng instance specifications

Specifications

Specification Code

vCPUs

Memory (GB)

Dedicated

gaussdb.mysql.xlarge.arm.4

4

16

gaussdb.mysql.xlarge.arm.8

4

32

gaussdb.mysql.2xlarge.arm.4

8

32

gaussdb.mysql.2xlarge.arm.8

8

64

gaussdb.mysql.4xlarge.arm.4

16

64

gaussdb.mysql.4xlarge.arm.8

16

128

gaussdb.mysql.8xlarge.arm.4

32

128

gaussdb.mysql.8xlarge.arm.8

32

256

gaussdb.mysql.12xlarge.arm.4

48

192

gaussdb.mysql.12xlarge.arm.8

48

384

gaussdb.mysql.15xlarge.arm.8

60

480
  • The DB instance specifications vary according to site requirements.
  • For information about Transactions Per Second (TPS) and Queries Per Second (QPS), see Performance White Paper.
Parent topic: Instance Description