Help Center/ TaurusDB/ Service Overview/
Updated on 2024-09-06 GMT+08:00
View PDF
Share

Billing

You only pay for what you use. There is no minimum charge.

Billing Item

Table 1 shows GaussDB(for MySQL) billing items.

Table 1 Billing items

Item

Billing Method

DB instance

Yearly/monthly or pay-per-use

Storage space

Yearly/monthly or pay-per-use

  • When you buy a yearly/monthly instance, you need to specify its storage. However, if the actual usage exceeds your purchased storage, you will be billed for additional storage on a pay-per-use basis.
  • When you buy a pay-per-use instance, you do not need to specify its storage, which will be scaled up dynamically based on the amount of data that needs to be stored, and is billed hourly on a pay-per-use basis.

Backup storage

GaussDB(for MySQL) provides storage space for backing up all of your provisioned database storage at no additional charge. If the backup storage usage exceeds 100% of your provisioned database storage, the additional part will be billed based on the backup storage pricing.

Public network traffic

GaussDB(for MySQL) instances are accessible from both private and public networks, but only the traffic from public networks is billed.

Monitoring by seconds

Pricing is listed on a per-hour basis, but bills are calculated based on the actual usage duration. GaussDB(for MySQL) provides monitoring every 60 seconds for free.

For details, see Product Pricing Details. You can use the price calculator to estimate the cost for your GaussDB(for MySQL) usage.

Billing Modes

GaussDB(for MySQL) provides the following two billing modes:

  • Yearly/Monthly: Provides a larger discount than pay-per-use billing and is recommended for long-term use. If the storage space of a yearly/monthly instance is full, the additional space will be billed on a pay-per-use basis.
  • Pay-per-Use (hourly): allows you to pay for only the resources you actually use. Pricing is listed on a per-hour basis, but bills are calculated down to the second.
  • Serverless: The resources of serverless DB instances automatically change based on application requirements. You can start using the DB instance first and then pay as you go.

Configuration Changes

  • Modifying instance specifications: You can change vCPUs and memory of instances based on service requirements. After the modification, you are billed based on the new specifications.
  • Changing storage: You can only change the storage of your yearly/monthly instances based on the amount of data that needs to be stored. After the change, you will be billed based on the new storage space. The storage can be scaled up or down only by a multiple of 10 GB.
  • Changing the compute configurations of a serverless instance: Serverless compute configurations scale up or down when CPU usage, memory usage, or buffer pool hit ratio met the following conditions.
    Table 2 Changing serverless compute resources

    Change Type

    Trigger Condition

    Scale up

    One of the following conditions is met:

    • The CPU usage is greater than 90% for 5 seconds and the interval between two scale-up operations is at least 5 seconds.
    • The memory usage is greater than 90% for 5 seconds and the interval between two scale-up operations is at least 5 seconds.

    Scale down

    One of the following conditions is met:

    • The CPU usage is less than 30% for 15 seconds and the interval between two scale-down operations is at least 15 seconds.
    • The memory usage is less than 30% for 15 seconds, the CPU usage is less than 70% for 15 seconds, and the interval between two scale-down operations is at least 15 seconds.