Deployment Guidelines

Resource Evaluation

Based on Table 1, you need to ensure that the resource usage is between 40% and 70%. If the resource usage is lower than 40%, capacity reduction is recommended. If the resource usage is higher than 70%, capacity expansion is recommended.

**Table 1** GaussDB rollout ledger
Component	Specification 1	Specification 2	Specification 3	Specification 4	Specification 5	MEM/CPU	File	Disk Capacity	Remarks
CN	8 vCPUs \| 64 GB	16 vCPUs \| 128 GB	32 vCPUs \| 256 GB	Arm: 60 vCPUs \| 480 GB x86: 64 vCPUs \| 512 GB	/	8	/var/chroot/var/lib/log	64 GB	Log disk
CN	8 vCPUs \| 64 GB	16 vCPUs \| 128 GB	32 vCPUs \| 256 GB	Arm: 60 vCPUs \| 480 GB x86: 64 vCPUs \| 512 GB	/	8	/var/chroot/usr/local	256 GB	Data disk
DN	8 vCPUs \| 64 GB	16 vCPUs \| 128 GB	32 vCPUs \| 256 GB	Arm: 60 vCPUs \| 480 GB x86: 64 vCPUs \| 512 GB	/	8	/var/chroot/var/lib/log	64 GB	Log disk
							/var/chroot/var/lib/engine/data	3,788 GB	Data disk
							/var/chroot/var/lib/log/backup	20 GB	Disk used to store the metadata of backups
GTM	4 vCPUs \| 32 GB	8 vCPUs \| 64 GB	16 vCPUs \| 128 GB	32 vCPUs \| 256 GB	Arm: 60 vCPUs \| 480 GB x86: 64 vCPUs \| 512 GB	8	/var/chroot/var/lib/log	32 GB	Log disk
GTM	1-9 shards	9-16 shards	16-32 shards	32-64 shards	More than 64 shards	8	/var/chroot/usr/local	32 GB	Data disk
CMS+ETCD	4 vCPUs \| 32 GB	8 vCPUs \| 64 GB	16 vCPUs \| 128 GB	32 vCPUs \| 256 GB	Arm: 60 vCPUs \| 480 GB x86: 64 vCPUs \| 512 GB	8	/var/chroot/var/lib/log	32 GB	Log disk
CMS+ETCD	1-9 shards	9-16 shards	16-32 shards	32-64 shards	More than 64 shards	8	/var/chroot/usr/local	64 GB	Data disk

Database Parameters

After the database is installed, the DBA needs to properly configure GUC parameters based on environment characteristics. GaussDB provides a default parameter template. If necessary, contact technical support to adjust parameters.

Parent topic: Database Design Guidelines

Previous topic: General Guidelines

Next topic: Database Object Naming Guidelines