Help Center/ GaussDB/ User Guide/ Instance Modifications/ Changing the CPU and Memory Specifications of a GaussDB Instance

Updated on 2025-09-05 GMT+08:00

View PDF

Changing the CPU and Memory Specifications of a GaussDB Instance

Scenarios

You can change the CPU and memory specifications of an instance to match your workload requirements. This includes scaling up or down the specifications of your GaussDB instance.

Precautions

Before you change the instance specifications, ensure that the instance is available. If the instance or node is abnormal, or the storage space is full, you cannot perform this operation.
During the specification change for an HA (1 primary + 2 standby) instance, a primary/standby failover is triggered. During the failover, services are interrupted for about 1 minute.
For a single-replica instance, changing instance specifications will reboot the instance and interrupt services for 5 to 10 minutes.
After you change instance specifications, the DB instances will be rebooted and services will be interrupted. You are advised to perform this operation during off-peak hours.
If the instance load is heavy, it takes a longer time to change its instance specifications.
If there is only one coordinator node in an instance, services will be interrupted during the specification change. Exercise caution when performing this operation.

Billing

Billing Mode	Operation	Impact on Fees
Yearly/Monthly	Specification upgrade	After instance specifications are upgraded, the new instance specifications take effect in the original usage period. You need to pay for the difference in price based on the remaining period. Example (The prices below are for reference only. The actual prices are displayed on the console.) Suppose you purchased a one-month, enterprise-edition 1 primary + 2 standby instance of V2.0-8.210 (instance specifications: dedicated, 4 vCPUs \| 16 GB; storage: ultra-high I/O, 160 GB) on June 1, 2025. The instance price was $2,064 USD/month. On June 15, 2025, you changed the instance specifications to 8 vCPUs \| 32 GB. The instance price became $4,032 USD/month. Price difference = Price for the new instance specifications x Remaining period – Price for the original instance specifications x Remaining period The remaining period in the formula is the number of remaining days in each calendar month divided by the maximum number of days in the calendar month. In this example, the remaining period and price difference are calculated as follows: Remaining period = 15 (Remaining days in June)/30 (Maximum number of days in June) = 0.5 Price difference = 4032 x 0.5 – 2064 x 0.5 = $984 USD
Yearly/Monthly	Specification downgrade	After instance specifications are downgraded, the new instance specifications take effect in the original usage period. GaussDB refunds the difference in price based on the remaining period. Example (The prices below are for reference only. The actual prices are displayed on the console.) Suppose you purchased a one-month, enterprise-edition 1 primary + 2 standby instance of V2.0-8.210 (instance specifications: dedicated, 8 vCPUs \| 32 GB; storage: ultra-high I/O, 160 GB) on June 1, 2025. The instance price was $4,032 USD/month. On June 15, 2025, you changed the instance specifications to 4 vCPUs \| 16 GB. The instance price became $2,064 USD/month. Price difference = Price for the original instance specifications x Remaining period – Price for the new instance specifications x Remaining period The remaining period in the formula is the number of remaining days in each calendar month divided by the maximum number of days in the calendar month. In this example, the remaining period and price difference are calculated as follows: Remaining period = 15 (Remaining days in June)/30 (Maximum number of days in June) = 0.5 Price difference = 4032 x 0.5 – 2064 x 0.5 = $984 USD
Pay-per-use	Specification upgrade	After instance specifications are changed, the new instance specifications are billed by hour. For details, see Product Pricing Details.
Pay-per-use	Specification downgrade

Procedure

Log in to the management console.
Click in the upper left corner and select a region and project.
Click in the upper left corner of the page and choose Databases > GaussDB.
On the Instances page, locate the instance and choose More > Change Instance Specifications in the Operation column.

Alternatively, click the instance name to go to the Basic Information page. In the Configuration area, click Change in the Instance Specifications field.
On the displayed page, specify the new instance specifications and click Next.
Confirm the specifications and click Submit.
View the new instance specifications.

After the task is submitted, click Go to Instance List. On the Instances page, the DB instance status is Changing instance specifications. After a few minutes, check the new instance specifications on the Basic Information page.