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 vCPU-to-memory ratio of 1:4), dedicated (with a vCPU-to-memory ratio of 1:8), and general-purpose (with a vCPU-to-memory ratio of 1:4)
Arm: Kunpeng dedicated (with a vCPU-to-memory ratio of 1:4) and Kunpeng dedicated (with a vCPU-to-memory ratio of 1:8)

**Table 1** Supported regions
Edition Type	Instance Type	Specification Type	Billing Mode	Region
Enterprise edition	Distributed	Dedicated (1:4) Dedicated (1:8) Kunpeng dedicated (1:4)	Pay-per-use and yearly/monthly	ME-Riyadh TR-Istanbul AP-Singapore LA-Sao Paulo1 AF-Johannesburg AP-Jakarta AP-Bangkok CN-Hong Kong LA-Mexico City2 CN Southwest-Guiyang1 LA-Santiago CN North-Beijing4 RU-Moscow2 CN East 2
		Kunpeng dedicated (1:8)	Pay-per-use	TR-Istanbul AP-Singapore AF-Johannesburg LA-Sao Paulo1 AP-Jakarta AP-Bangkok CN-Hong Kong LA-Mexico City2 CN Southwest-Guiyang1 LA-Santiago CN North-Beijing4 RU-Moscow2 CN East 2
		Kunpeng dedicated (1:8)	Yearly/Monthly	AP-Singapore LA-Sao Paulo1 AF-Johannesburg AP-Jakarta AP-Bangkok CN-Hong Kong LA-Mexico City2 CN Southwest-Guiyang1 LA-Santiago CN North-Beijing4 RU-Moscow2 CN East 2
	Centralized	Dedicated (1:4) Dedicated (1:8) Kunpeng dedicated (1:4) Kunpeng dedicated (1:8)	Pay-per-use and yearly/monthly	ME-Riyadh TR-Istanbul AP-Singapore AF-Johannesburg LA-Sao Paulo1 AP-Bangkok AP-Jakarta CN-Hong Kong LA-Mexico City2 LA-Santiago CN Southwest-Guiyang1 CN North-Beijing4 RU-Moscow2 CN East 2
Basic edition	Distributed	Dedicated (1:4) Dedicated (1:8) Kunpeng dedicated (1:4)	Pay-per-use	ME-Riyadh AF-Johannesburg LA-Sao Paulo1 CN-Hong Kong CN South-Guangzhou LA-Santiago AP-Singapore TR-Istanbul CN Southwest-Guiyang1 AP-Bangkok LA-Mexico City2 CN East-Shanghai1 CN North-Beijing4 AP-Jakarta CN East 2
	Distributed	Kunpeng dedicated (1:8)	Pay-per-use	CN South-Guangzhou CN East-Shanghai1 CN Southwest-Guiyang1 CN North-Beijing4 CN East 2
	Centralized	General-purpose (1:4) Dedicated (1:4) Dedicated (1:8) Kunpeng dedicated (1:4)	Pay-per-use	ME-Riyadh AP-Jakarta AF-Johannesburg CN South-Guangzhou LA-Sao Paulo1 LA-Mexico City2 CN-Hong Kong CN East-Shanghai1 CN North-Beijing4 CN Southwest-Guiyang1 TR-Istanbul AP-Singapore AP-Bangkok LA-Santiago CN East 2
	Centralized	Kunpeng dedicated (1:8)	Pay-per-use	CN East-Shanghai1 CN South-Guangzhou CN Southwest-Guiyang1 CN North-Beijing4 CN East 2

**Table 2** Instance specifications
Edition 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
			24	96	3000
			32	128	3000
			48	192	3000
			64	256	4,000
			96	384	6000
		Dedicated (1:8) NOTE: Dedicated (1:8) is based on the x86 architecture.	8	64	1,000
			16	128	2,000
			24	192	3000
			32	256	4,000
			48	384	6000
			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
			24	96	3000
			32	128	2,000
			48	192	3000
			64	256	4,000
			96	384	3000
		Kunpeng dedicated (1:8) NOTE: Kunpeng dedicated (1:8) is based on the Arm architecture.	8	64	1,000
			16	128	2,000
			24	192	3000
			32	256	4,000
			48	384	6000
			60	480	8,000
	Centralized	Dedicated (1:4) NOTE: Dedicated (1:4) is based on the x86 architecture.	4	16	300
			8	32	600
			16	64	2,048
			24	96	2048
			32	128	5,000
			48	192	3000
			96	384	6000
		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 centralized instances of version V2.0-2.6 or later can be used in the production environment.	2,048
			16	128	5,000
			24	192	3000
			32	256	11,000
			48	384	6000
			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
			24	96	2048
			32	128	5,000
			48	192	3000
			96	384	6000
		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 centralized instances of version V2.0-2.6 or later can be used in the production environment.	2,048
			16	128	5,000
			24	192	3000
			32	256	11,000
			48	384	6000
			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
	Centralized	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