Updated on 2026-10-19 GMT+08:00

Changing the Compute Range of a Serverless Instance

Scenarios

After buying a serverless instance, you can change its compute range. When certain trigger conditions are met, instance compute is automatically changed.

Trigger Conditions for Compute Changes

Cloud Eye monitors the CPU usage and memory usage of serverless instances. If certain conditions are met, a compute change will be triggered. Table 1 lists the trigger conditions.

**Table 1** Trigger conditions for compute changes
Change Type	Trigger Condition
Compute scale-up	If any of the following conditions is met, a compute scale-up is automatically triggered: The CPU usage remains above 80% for 4 seconds, and the interval since the last scale-up is at least 1 second. The memory usage remains above 80% for 4 seconds, and the interval since the last scale-up is at least 1 second. The CPU usage remains above 60% for 20 seconds, and the interval since the last scale-up is at least 10 seconds.
Compute scale-down	The CPU usage remains below 30% for 10 seconds, the interval since the last scale-down is at least 20 seconds, and the memory usage after scale-down does not exceed 80%.

Constraints

As data grows, there may be some cache or memory fragments that cannot be released, leading to high memory usage. If you want to reduce compute to the minimum, you can reboot the instance.
If resources are insufficient when you change the compute range, nodes with the target specifications will be created on physical machines that have sufficient resources. The task center will display the serverless cross-node scale-out task. If resources on the primary node are insufficient, a primary/standby failover will be performed.
For a serverless instance or a fixed-specification instance with serverless nodes, a compute range change cannot be triggered when you add or delete read replicas.

Changing the Compute Range

Log in to the TaurusDB console.
Click in the upper left corner and select a region.
On the Instances page, click the instance name to go to the Basic Information page.
In the Serverless Information area, click Change under Compute Range.

Figure 1 Changing serverless information
In the displayed dialog box, modify Min. Compute and Max. Compute. If Node Compute Synchronization is set to Yes, the current compute of any node below Min. Compute is updated to Min. Compute while the compute range is being modified.

Figure 2 Changing the compute range
Click OK.
Check the new compute range in the Serverless Information area.

APIs

Parent Topic: Serverless Instances