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 instances support both dedicated and general-purpose specifications.
- Dedicated: 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.
- General-purpose: The vCPUs and memory are shared with other general-purpose instances on the same physical machine. vCPU usage is maximized through resource overcommitment. General-purpose instances are cost-effective and suitable for scenarios where stable performance is not critical.
|
Specifications |
Specification Code |
vCPUs |
Memory (GB) |
Supported Regions |
|---|---|---|---|---|
|
Dedicated |
gaussdb.mysql.large.x86.4 |
2 |
8 |
CN North-Beijing4, CN North-Ulanqab1 |
|
CN East-Shanghai1 |
||||
|
CN South-Guangzhou |
||||
|
CN Southwest-Guiyang1 |
||||
|
CN-Hong Kong |
||||
|
AP-Singapore, AP-Jakarta |
||||
|
ME-Riyadh |
||||
|
AF-Johannesburg |
||||
|
TR-Istanbul |
||||
|
gaussdb.mysql.large.x86.8 |
2 |
16 |
CN North-Ulanqab1 |
|
|
CN Southwest-Guiyang1 |
||||
|
AP-Singapore |
||||
|
AF-Johannesburg |
||||
|
gaussdb.mysql.xlarge.x86.4 |
4 |
16 |
CN North-Beijing4, CN North-Ulanqab1 |
|
|
CN East-Shanghai1 |
||||
|
CN South-Guangzhou |
||||
|
CN Southwest-Guiyang1 |
||||
|
CN-Hong Kong |
||||
|
AP-Bangkok, AP-Singapore, AP-Jakarta |
||||
|
ME-Riyadh |
||||
|
AF-Johannesburg |
||||
|
TR-Istanbul |
||||
|
gaussdb.mysql.xlarge.x86.8 |
4 |
32 |
CN North-Ulanqab1 |
|
|
CN Southwest-Guiyang1 |
||||
|
AP-Singapore |
||||
|
AF-Johannesburg |
||||
|
gaussdb.mysql.2xlarge.x86.4 |
8 |
32 |
CN North-Beijing4, CN North-Ulanqab1 |
|
|
CN East-Shanghai1 |
||||
|
CN South-Guangzhou |
||||
|
CN Southwest-Guiyang1 |
||||
|
CN-Hong Kong |
||||
|
AP-Bangkok, AP-Singapore, AP-Jakarta |
||||
|
ME-Riyadh |
||||
|
AF-Johannesburg |
||||
|
TR-Istanbul |
||||
|
gaussdb.mysql.2xlarge.x86.8 |
8 |
64 |
CN North-Ulanqab1 |
|
|
CN Southwest-Guiyang1 |
||||
|
AP-Singapore |
||||
|
AF-Johannesburg |
||||
|
gaussdb.mysql.4xlarge.x86.4 |
16 |
64 |
CN North-Beijing4, CN North-Ulanqab1 |
|
|
CN East-Shanghai1 |
||||
|
CN South-Guangzhou |
||||
|
CN Southwest-Guiyang1 |
||||
|
CN-Hong Kong |
||||
|
AP-Bangkok, AP-Singapore, AP-Jakarta |
||||
|
ME-Riyadh |
||||
|
AF-Johannesburg |
||||
|
TR-Istanbul |
||||
|
gaussdb.mysql.4xlarge.x86.8 |
16 |
128 |
CN North-Ulanqab1 |
|
|
CN Southwest-Guiyang1 |
||||
|
AP-Singapore |
||||
|
AF-Johannesburg |
||||
|
gaussdb.mysql.8xlarge.x86.4 |
32 |
128 |
CN North-Beijing4, CN North-Ulanqab1 |
|
|
CN East-Shanghai1 |
||||
|
CN South-Guangzhou |
||||
|
CN Southwest-Guiyang1 |
||||
|
CN-Hong Kong |
||||
|
AP-Bangkok, AP-Singapore, AP-Jakarta |
||||
|
ME-Riyadh |
||||
|
AF-Johannesburg |
||||
|
TR-Istanbul |
||||
|
gaussdb.mysql.8xlarge.x86.8 |
32 |
256 |
CN North-Ulanqab1 |
|
|
CN Southwest-Guiyang1 |
||||
|
AP-Singapore |
||||
|
AF-Johannesburg |
||||
|
gaussdb.mysql.16xlarge.x86.4 |
60 |
256 |
CN North-Beijing4, CN North-Ulanqab1 |
|
|
CN East-Shanghai1 |
||||
|
CN South-Guangzhou |
||||
|
CN Southwest-Guiyang1 |
||||
|
CN-Hong Kong |
||||
|
AP-Bangkok, AP-Singapore, AP-Jakarta |
||||
|
ME-Riyadh |
||||
|
AF-Johannesburg |
||||
|
TR-Istanbul |
||||
|
gaussdb.mysql.16xlarge.x86.8 |
64 |
512 |
CN North-Ulanqab1 |
|
|
CN Southwest-Guiyang1 |
||||
|
AP-Singapore |
||||
|
AF-Johannesburg |
||||
|
gaussdb.mysql.21xlarge.x86.8 |
84 |
672 |
TR-Istanbul |
|
|
General-purpose |
gaussdb.mysql.large.x86.normal.2 |
2 |
4 |
CN North-Beijing4 |
|
CN Southwest-Guiyang1 |
||||
|
CN East-Shanghai1 |
||||
|
CN South-Guangzhou |
||||
|
CN-Hong Kong |
||||
|
gaussdb.mysql.large.x86.normal.4 |
2 |
8 |
CN North-Beijing4 |
|
|
CN Southwest-Guiyang1 |
||||
|
gaussdb.mysql.xlarge.x86.normal.2 |
4 |
8 |
CN North-Beijing4 |
|
|
CN Southwest-Guiyang1 |
||||
|
CN East-Shanghai1 |
||||
|
CN South-Guangzhou |
||||
|
CN-Hong Kong |
||||
|
gaussdb.mysql.xlarge.x86.normal.4 |
4 |
16 |
CN North-Beijing4 |
|
|
CN Southwest-Guiyang1 |
||||
|
gaussdb.mysql.2xlarge.x86.normal.2 |
8 |
16 |
CN North-Beijing4 |
|
|
CN Southwest-Guiyang1 |
||||
|
CN East-Shanghai1 |
||||
|
CN South-Guangzhou |
||||
|
CN-Hong Kong |
||||
|
gaussdb.mysql.2xlarge.x86.normal.4 |
8 |
32 |
CN North-Beijing4 |
|
|
CN Southwest-Guiyang1 |
||||
|
gaussdb.mysql.4xlarge.x86.normal.2 |
16 |
32 |
CN North-Beijing4 |
|
|
CN Southwest-Guiyang1 |
||||
|
CN East-Shanghai1 |
||||
|
CN South-Guangzhou |
||||
|
CN-Hong Kong |
||||
|
gaussdb.mysql.4xlarge.x86.normal.4 |
16 |
64 |
CN North-Beijing4 |
|
|
CN Southwest-Guiyang1 |
||||
|
gaussdb.mysql.8xlarge.x86.normal.2 |
32 |
64 |
CN North-Beijing4 |
|
|
CN Southwest-Guiyang1 |
||||
|
CN East-Shanghai1 |
||||
|
CN South-Guangzhou |
||||
|
CN-Hong Kong |
||||
|
gaussdb.mysql.8xlarge.x86.normal.4 |
32 |
128 |
CN North-Beijing4 |
|
|
CN Southwest-Guiyang1 |
- 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 instances only support dedicated specifications.
Dedicated: 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.
|
Specifications |
Specification Code |
vCPUs |
Memory (GB) |
Supported Regions |
|---|---|---|---|---|
|
Dedicated |
gaussdb.mysql.xlarge.arm.4 |
4 |
16 |
CN North-Beijing4, CN North-Ulanqab1 |
|
CN East-Shanghai1 |
||||
|
CN South-Guangzhou |
||||
|
AP-Singapore |
||||
|
gaussdb.mysql.xlarge.arm.8 |
4 |
32 |
CN North-Beijing4 |
|
|
CN East-Shanghai1 |
||||
|
CN South-Guangzhou |
||||
|
CN Southwest-Guiyang1 |
||||
|
AP-Singapore |
||||
|
gaussdb.mysql.2xlarge.arm.4 |
8 |
32 |
CN North-Beijing4, CN North-Ulanqab1 |
|
|
CN East-Shanghai1 |
||||
|
CN South-Guangzhou |
||||
|
AP-Singapore |
||||
|
gaussdb.mysql.2xlarge.arm.8 |
8 |
64 |
CN North-Beijing4 |
|
|
CN East-Shanghai1 |
||||
|
CN South-Guangzhou |
||||
|
CN Southwest-Guiyang1 |
||||
|
AP-Singapore |
||||
|
gaussdb.mysql.4xlarge.arm.4 |
16 |
64 |
CN North-Beijing4, CN North-Ulanqab1 |
|
|
CN East-Shanghai1 |
||||
|
CN South-Guangzhou |
||||
|
AP-Singapore |
||||
|
gaussdb.mysql.4xlarge.arm.8 |
16 |
128 |
CN North-Beijing4 |
|
|
CN East-Shanghai1 |
||||
|
CN South-Guangzhou |
||||
|
CN Southwest-Guiyang1 |
||||
|
AP-Singapore |
||||
|
gaussdb.mysql.8xlarge.arm.4 |
32 |
128 |
CN North-Beijing4, CN North-Ulanqab1 |
|
|
CN East-Shanghai1 |
||||
|
CN South-Guangzhou |
||||
|
AP-Singapore |
||||
|
gaussdb.mysql.8xlarge.arm.8 |
32 |
256 |
CN North-Beijing4 |
|
|
CN Southwest-Guiyang1 |
||||
|
AP-Singapore |
||||
|
gaussdb.mysql.12xlarge.arm.4 |
48 |
192 |
CN North-Beijing4, CN North-Ulanqab1 |
|
|
CN East-Shanghai1 |
||||
|
CN South-Guangzhou |
||||
|
AP-Singapore |
||||
|
gaussdb.mysql.12xlarge.arm.8 |
48 |
384 |
CN North-Beijing4 |
|
|
CN East-Shanghai1 |
||||
|
CN South-Guangzhou |
||||
|
CN Southwest-Guiyang1 |
||||
|
AP-Singapore |
||||
|
gaussdb.mysql.15xlarge.arm.8 |
60 |
480 |
CN North-Beijing4 |
|
|
CN East-Shanghai1 |
||||
|
CN South-Guangzhou |
||||
|
CN Southwest-Guiyang1 |
||||
|
AP-Singapore |
- 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.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot
