Cost Optimization

Resource Optimization

Cloud Eye helps you monitor resource usage, identify idle resources, and find opportunities to save costs. You can also identify resources with high costs based on the results of Cost Analysis and take optimization measures accordingly.

• View GaussDB(for MySQL) monitoring metrics on Cloud Eye, such as the CPU, memory, and disk usage. If the current configuration is too high, you can reduce the configuration by changing the specifications.
• Monitor idle GaussDB(for MySQL) resources and deletes idle instances in a timely manner.
• If your services have low requirements on performance and stability, purchase a general-purpose DB instance to reduce your costs. For example, in the same specifications (32 vCPUs and 128 GB of memory), the cost of a general-purpose DB instance is 30% lower than that of a dedicated DB instance.

Billing Mode Selection

Different types of services have different requirements on resource usage periods, so the most economical billing mode for one resource may not be the best option for another resource.

• For mature services that tend to be stable for the long term, select yearly/monthly billing.
• For short-term, unpredictable services that experience traffic bursts and cannot afford to be interrupted, select pay-per-use billing.
• Monitor the lifecycle of instances and renew yearly/monthly resources that are about to expire in a timely manner.

Automatic O&M

• For yearly/monthly and pay-per-use DB instances: Configure auto scaling policies for DB instances on the Basic Information page. When configuring auto scaling policies, you can enable or disable Auto Scale-up or Auto Scale-down. The scaling type includes changing instance specifications or the number of read replicas. For details, see Configuring Auto Scaling Policies.
• Serverless instances: Configure minimum billing unit and scaling scope for DB instances. DB instance resources automatically grow based on workload. For details, see Step 1: Buy a DB Instance.