Instance Specifications
GaussDB instances in different regions support x86 or Arm architecture. For details, see Table 1. GaussDB instances also support different specifications. For details, see Table 2.
- x86: Dedicated (with a CPU-to-memory ratio of 1:4), dedicated (with a CPU-to-memory ratio of 1:8), and general-purpose (with a CPU-to-memory ratio of 1:4)
- Arm: Kunpeng dedicated (with a CPU-to-memory ratio of 1:4) and Kunpeng dedicated (with a CPU-to-memory ratio of 1:8)
Instance Type |
Specification Type |
Billing Mode |
Region |
---|---|---|---|
Distributed |
Dedicated (1:4) |
Pay-per-use |
AP-Singapore |
CN East-Shanghai1 |
|||
CN North-Beijing4 |
|||
CN South-Guangzhou |
|||
CN Southwest-Guiyang1 |
|||
AF-Johannesburg |
|||
LA-Sao Paulo1 |
|||
Yearly/monthly |
AP-Singapore |
||
CN East-Shanghai1 |
|||
CN North-Beijing4 |
|||
CN South-Guangzhou |
|||
CN Southwest-Guiyang1 |
|||
AF-Johannesburg |
|||
LA-Sao Paulo1 |
|||
Kunpeng dedicated (1:8) |
Pay-per-use |
AP-Singapore |
|
CN East-Shanghai1 |
|||
CN North-Beijing4 |
|||
CN South-Guangzhou |
|||
CN Southwest-Guiyang1 |
|||
AF-Johannesburg |
|||
LA-Sao Paulo1 |
|||
Yearly/monthly |
AP-Singapore |
||
CN East-Shanghai1 |
|||
CN North-Beijing4 |
|||
CN South-Guangzhou |
|||
CN Southwest-Guiyang1 |
|||
AF-Johannesburg |
|||
LA-Sao Paulo1 |
|||
General-purpose (1:4) |
Pay-per-use |
AP-Singapore |
|
CN East-Shanghai1 |
|||
CN North-Beijing4 |
|||
CN South-Guangzhou |
|||
CN Southwest-Guiyang1 |
|||
AF-Johannesburg |
|||
LA-Sao Paulo1 |
|||
Yearly/monthly |
AP-Singapore |
||
CN East-Shanghai1 |
|||
CN North-Beijing4 |
|||
CN South-Guangzhou |
|||
CN Southwest-Guiyang1 |
|||
AF-Johannesburg |
|||
LA-Sao Paulo1 |
|||
Primary/Standby |
Dedicated (1:4) |
Pay-per-use |
AP-Singapore |
CN East-Shanghai1 |
|||
CN North-Beijing4 |
|||
CN South-Guangzhou |
|||
CN Southwest-Guiyang1 |
|||
AF-Johannesburg |
|||
LA-Sao Paulo1 |
|||
Yearly/monthly |
AP-Singapore |
||
CN East-Shanghai1 |
|||
CN North-Beijing4 |
|||
CN South-Guangzhou |
|||
CN Southwest-Guiyang1 |
|||
AF-Johannesburg |
|||
LA-Sao Paulo1 |
|||
General-purpose (1:4) |
Pay-per-use |
AP-Singapore |
|
CN East-Shanghai1 |
|||
CN North-Beijing4 |
|||
CN South-Guangzhou |
|||
CN Southwest-Guiyang1 |
|||
AF-Johannesburg |
|||
LA-Sao Paulo1 |
|||
Yearly/monthly |
AP-Singapore |
||
CN East-Shanghai1 |
|||
CN North-Beijing4 |
|||
CN South-Guangzhou |
|||
CN Southwest-Guiyang1 |
|||
AF-Johannesburg |
|||
LA-Sao Paulo1 |
Service Type |
DB Instance Type |
Specification Type |
vCPUs |
Memory (GB) |
Default Maximum Connections (Per CN) |
---|---|---|---|---|---|
Enterprise edition |
Distributed |
Dedicated (1:4)
NOTE:
Dedicated (1:4) is based on the x86 architecture. |
8 |
32 |
100 |
16 |
64 |
1,000 |
|||
32 |
128 |
2,000 |
|||
64 |
256 |
4,000 |
|||
Dedicated (1:8)
NOTE:
Dedicated (1:8) is based on the x86 architecture. |
8 |
64 |
1,000 |
||
16 |
128 |
2,000 |
|||
32 |
256 |
4,000 |
|||
64 |
512 |
8,000 |
|||
Kunpeng dedicated (1:4)
NOTE:
Kunpeng dedicated (1:4) is based on the Arm architecture. |
8 |
32 |
100 |
||
16 |
64 |
1,000 |
|||
32 |
128 |
2,000 |
|||
64 |
256 |
4,000 |
|||
Kunpeng dedicated (1:8)
NOTE:
Kunpeng dedicated (1:8) is based on the Arm architecture. |
8 |
64 |
1,000 |
||
16 |
128 |
2,000 |
|||
32 |
256 |
4,000 |
|||
60 |
480 |
8,000 |
|||
Primary/Standby |
Dedicated (1:4)
NOTE:
Dedicated (1:4) is based on the x86 architecture. |
4 |
16 |
300 |
|
8 |
32 |
600 |
|||
16 |
64 |
2,048 |
|||
32 |
128 |
5,000 |
|||
Dedicated (1:8)
NOTE:
Dedicated (1:8) is based on the x86 architecture. |
4 |
32
NOTE:
This specification is not available for production environments, but you can submit a service ticket to request it at Service Tickets > Create Service Ticket in the upper right corner of the management console. |
600 |
||
8 |
64
NOTE:
Only primary/standby instances of version 2.6 or later can be used in the production environment. |
2,048 |
|||
16 |
128 |
5,000 |
|||
32 |
256 |
11,000 |
|||
64 |
512 |
25,000 |
|||
Kunpeng dedicated (1:4)
NOTE:
Kunpeng dedicated (1:4) is based on the Arm architecture. |
4 |
16 |
300 |
||
8 |
32 |
600 |
|||
16 |
64 |
2,048 |
|||
32 |
128 |
5,000 |
|||
Kunpeng dedicated (1:8)
NOTE:
Kunpeng dedicated (1:8) is based on the Arm architecture. |
4 |
32
NOTE:
This specification is not available for production environments, but you can submit a service ticket to request it at Service Tickets > Create Service Ticket in the upper right corner of the management console. |
600 |
||
8 |
64
NOTE:
Only primary/standby instances of version 2.6 or later can be used in the production environment. |
2,048 |
|||
16 |
128 |
5,000 |
|||
32 |
256 |
11,000 |
|||
60 |
480 |
24,000 |
|||
Basic edition |
Distributed |
Dedicated (1:4)
NOTE:
Dedicated (1:4) is based on the x86 architecture. |
16 |
64 |
200 |
32 |
128 |
350 |
|||
64 |
256 |
900 |
|||
Dedicated (1:8)
NOTE:
Dedicated (1:8) is based on the x86 architecture. |
16 |
128 |
350 |
||
32 |
256 |
900 |
|||
64 |
512 |
2,000 |
|||
Kunpeng dedicated (1:4)
NOTE:
Kunpeng dedicated (1:4) is based on the Arm architecture. |
16 |
64 |
200 |
||
32 |
128 |
350 |
|||
Kunpeng dedicated (1:8)
NOTE:
Kunpeng dedicated (1:8) is based on the Arm architecture. |
16 |
128 |
350 |
||
32 |
256 |
900 |
|||
60 |
480 |
1,800 |
|||
Primary/Standby |
General-purpose (1:4)
NOTE:
General-purpose (1:4) is based on the x86 architecture. |
4 |
16 |
300 |
|
8 |
32 |
600 |
|||
Dedicated (1:4)
NOTE:
Dedicated (1:4) is based on the x86 architecture. |
4 |
16 |
300 |
||
8 |
32 |
600 |
|||
16 |
64 |
2,048 |
|||
32 |
128 |
5,000 |
|||
64 |
256 |
11,000 |
|||
Kunpeng dedicated (1:4)
NOTE:
Kunpeng dedicated (1:4) is based on the Arm architecture. |
4 |
16 |
300 |
||
8 |
32 |
600 |
|||
16 |
64 |
2,048 |
|||
32 |
128 |
5,000 |
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