A computing resource package is a prepaid resource type launched by TDSQL-C for MySQL. It can be used to deduct the computing resources used by Serverless instances. The resource packages will not affect the pay-as-you-go billing mode of Serverless computing resources. After a resource package is used, settlement is performed per hour by deducting the actual usage from your purchased resource package. In this way, you can benefit from the preferential computing resource prices while enjoying the high-precision billing mode of Serverless. This document describes the specification types and prices of computing resource packages.
Specification Types and Prices
|
| 400–10,000 thousand CCU (10,000 exclusive) | 6-month validity period: 0.0119 1-year validity period: 0.0126 | 6-month validity period: 0.013 1-year validity period: 0.0138 |
| 10,000–40,000 thousand CCU (40,000 exclusive) | 6-month validity period: 0.0112 1-year validity period: 0.0119 | 6-month validity period: 0.0122 1-year validity period: 0.013 |
| 40,000–200,000 thousand CCU (200,000 exclusive) | 6-month validity period: 0.0105 1-year validity period: 0.0112 | 6-month validity period: 0.0115 1-year validity period: 0.0122 |
Note:
TDSQL-C Compute Unit (CCU) is the computing and billing unit for the serverless instance. A CCU is approximately equal to 1 CPU core and 2 GB memory. The number of CCUs used in each billing cycle is the greater of the number of CPU cores used by the database and 1/2 of the memory size.
Case
We will compare the compute resource fees of two instances (one without a compute resource package and the other with a compute resource package) to more intuitively understand the cost difference between using and not using a compute resource package.
Case background
Region: Beijing.
Instance Mode: Single-Node Edition.
The first instance: Unused compute resource package will be billed on a pay-as-you-go basis, denoted as Instance A.
The second instance: Used the compute resource package, the basic edition of the compute resource package is purchased and bound, with a CCU amount of 400,000 and a validity period of 6 months. Denote it as Instance B.
Operation scenario: Instance A and Instance B each continued to run at 1 CCU per second (equal to 1 core 2GB full load per second) for 10 hours. The compute resource fees of these 10 hours are calculated and compared below.
Cost comparison
|
Billing formula | compute resource fees = serverless compute unit price × CCU amount | Compute resource fees = Serverless compute unit price × CCU amount |
Billing model | pay as you go | compute resource pack |
Serverless compute unit price | 0.00001397 USD per unit | 0.0119 USD per 10,000 CCU，equal to 0.00000119 USD per unit |
CCU amount | 36000 calculated based on the running scenario, instance A continues to run at 1 CCU per second for 10 hours, then the total CCU amount for 10 hours is: 1 CCU x 3600 seconds x 10 hours = 36,000 | 36000 calculated based on the running scenario, instance B continues to run at 1 CCU per second for 10 hours, then the total CCU amount for 10 hours is: 1 CCU x 3600 seconds x 10 hours = 36,000 |
Compute resource fees | 0.00001397 x 36000 = 0.50 USD | 0.00000119 x 36000 = 0.04 USD |
Subsequent billing | subsequent operations of instance A will continue to use pay-as-you-go billing, resulting in new fees | Instance B purchased a total compute resource package of 400,000 CCU. In the past 10 hours, 36,000 CCU were consumed, and the remaining amount was 364,000 CCU. This compute resource package will continue to be consumed in the future until the computing resource package is consumed or expires. Instance B will return to pay-as-you-go billing. You can also continue to purchase and bind other compute resource packages before the compute resource package is consumed. |
Compare results
It can be seen from the above comparison that since the unit price of Serverless compute in a compute resource package is lower than that of pay-as-you-go, the overall compute resource fees is reduced, and it is more favorable to use a compute resource package. The unit prices of compute resource packages for Basic Edition, General Edition, and Enterprise Edition are different. You can choose the appropriate specification type based on the actual amount of CCU required.
Note
The compute resource pack will be deducted based on the actual CCU usage per second, which is more cost-effective and flexible than the pay-as-you-go option. Before the deduction of the serverless cluster, you must first bind a compute resource pack. The cluster will not be terminated when the resource pack is unbound, used up, or expires. It will instead be billed on a pay-as-you-go basis. It is important to note the following points:
Compute resource packs are classified into two types: those for the Chinese mainland and those for regions outside the Chinese mainland. Each type is specified to be shared by all serverless clusters in the region, that is, one compute resource pack can be shared by multiple serverless clusters.
A serverless cluster can be bound to a maximum of ten compute resource packs, with support for adjusting the consumption priority order of multiple compute resource packs. The cluster will consume resources in ascending order based on the priority level numbers. A compute resource pack is deducted based on the accumulated usage per second.
A compute resource pack doesn’t support downgrade once purchased.
Management
Refund
For resource packages that remain unused within their validity periods, each Tencent Cloud account (root account) is eligible for a maximum of 20 refund instances per calendar year. Refunds are not available for resource packages that have either expired or been fully used. For detailed refund instructions, please see the Requesting Refund for Resource Package. Note：
Regarding the limitations on the number of refunds, the system calculates this on a calendar year basis. The first calendar year cycle is from June 30, 2023, at 23:59:59 to July 1, 2024, at 00:00:00. The count resets annually on July 1 at 00:00:00. Therefore, the second calendar year cycle is from July 1, 2024, at 00:00:00 to June 30, 2025, at 23:59:59, and so on.
Relevant Documents
Related APIs
|
| This API (CreateResourcePackage) is used to purchase new resource pack. |