Changing the Compute Range

Conditions for Changing Compute

Cloud Eye monitors the CPU usage and memory usage of serverless instances.

If any of the following conditions is met, a compute scale-up is automatically triggered:

• The CPU usage is greater than 80% for 5 seconds and it has been at least 5 seconds since the last scale-up.
• The memory usage is greater than 80% for 5 seconds and it has been at least 5 seconds since the last scale-up.
• The CPU usage is greater than 60% for 20 seconds and it has been at least 10 seconds since the last scale-up.

If the following condition is met, a compute scale-down is automatically triggered:

The CPU usage is less than 30% for 15 seconds, it has been at least 15 seconds since the last scale-down, and the memory usage is 80% or less.

Constraints

• As data grows and with daily usage, 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 a compute change is triggered, nodes with the desired specifications will be created on a physical machine that has enough resources. If resources on the primary node are insufficient, there will be a primary/standby failover.

Changing the Compute Range

1. Log in to the management console.
2. Click in the upper left corner and select a region and project.
3. Click in the upper left corner of the page and choose Databases > GaussDB(for MySQL).
4. On the Instances page, click the instance name to go to the Basic Information page.
5. In the Serverless Information area, click Change under Compute Range.
   Figure 1 Changing serverless information
   

6. In the displayed dialog box, set Min. Compute and Max. Compute, and click OK.
   Figure 2 Changing the compute range
   

7. Check the new compute range in the Serverless Information area.