Billing Overview
Billing Mode
TencentDB for MySQL offers the following two billing modes:
Billing Mode | Payment Mode | Scenarios |
Yearly/monthly subscription | Prepaid mode, which means paying fees when a new instance is created. | Suitable for long-term needs with relatively stable traffic volume. The fee is lower compared to pay-as-you-go mode, and the longer the purchase period, the more discounts you get. |
Pay-as-you-go | Postpaid mode, which means applying for resources on demand first, and fees are charged based on your actual resource usage during settlement. | It is suitable for business senarios with large instantaneous fluctuations in business volume. The instance can be released immediately after use to save costs. |
Instance Price
Billing Formula
Total cost = Memory and CPU cost + Storage space cost + Backup space cost + Traffic cost (currently free)
Billable Item
Billable Item | Description |
Memory and CPU fees | The cost of the instance specifications (including memory and CPU) selected on the purchase page supports tiered pricing for both yearly/monthly subscription and pay-as-you-go. For pricing details, see Product Pricing. Pay-as-you-go adopts a three-tiered pricing model: the longer the usage, the greater the discount. Tier 1 (T1): 0 hours < T1 ≤ 96 hours; Tier 2 (T2): 96 hours < T2 ≤ 360 hours; Tier 3 (T3): T3 > 360 hours. |
Storage space fees | The cost of the disk size selected on the purchase page supports both yearly/monthly subscription and pay-as-you-go billing. For pricing details, see Product Pricing. The storage space is used for storing data files, shared tablespaces, error log files, REDO LOG, UNDO LOG, data dictionaries, binlog, and other files necessary for TencentDB for MySQL operation. |
Backup space fees | TencentDB for MySQL provides a certain amount of free backup space per region. The free backup space size equals the sum of the storage space of all two-node and three-node instances (including source instances and disaster recovery instances) in the corresponding region. For fees beyond the free backup space, see Backup Space Billing. |
Traffic fees | Public network traffic fees are currently free. |
You can directly use the Price Calculator to check the combined pricing for your required products to estimate resource costs. To ensure price accuracy, please log in to Tencent Cloud before checking.
Note:
The disk fee (storage space fee) of a read-only instance is consistent with that of the primary instance. You can see Product Pricing for details, as shown below.
Read-Only Analysis Engine Pricing Overview
The billing formula for TencentDB for MySQL read-only analysis engines is as follows:
When a single node is selected: Total cost of the read-only analysis engine = cost of computing resources for a single node + unit price of storage space × purchased storage space
When multiple nodes are selected: Total cost of the read-only analysis engine = total computing resource cost of multiple nodes (cost corresponding to total computing resources) + total storage space of all nodes × unit price of storage space
Note:
When multiple nodes are selected, the number of nodes to purchase can be chosen as 2 or 3.
Compute Node Pricing of Read-Only Analysis Engine
When creating a read-only analysis engine instance, you can select the number of nodes. For a single node, the default number of nodes is 1. For multiple nodes, you can choose 2 or 3 nodes. The unit price of computing resources differs between single-node and multi-node configurations. You can refer to the table below for details.
Instance Type | Compute Node Specifications | Beijing, Shanghai, Guangzhou, Chengdu, and Nanjing | Hong Kong (China) | Singapore, Virginia, São Paulo, and Frankfurt | |||
| | Yearly/Monthly Subscription Price (USD/Month) | Pay-as-You-Go Price (USD/Hour) | Yearly/Monthly Subscription Price (USD/Month) | Pay-as-You-Go Price (USD/Hour) | Yearly/Monthly Subscription Price (USD/Month) | Pay-as-You-Go Price (USD/Hour) |
General | 4-core 16 GB single-node | 64.28571429 | 0.13392857 | 107.3571429 | 0.22366071 | 156.25 | 0.325 |
General | 8-core 32 GB single-node | 100 | 0.20833333 | 167 | 0.34791666 | 312.5 | 0.65 |
General | 16-core 64 GB single-node | 200 | 0.41666667 | 334 | 0.69583333 | 625 | 1.3 |
General | 24-core 96 GB single-node | 535.71428571 | 1.11607143 | 894.6428571 | 1.86383928 | 937.5 | 1.953125 |
General | 32-core 128 GB single-node | 714.28571429 | 1.48809524 | 1192.857143 | 2.48511905 | 1250 | 2.60416667 |
General | 64-core 256 GB single-node | 1428.57142857 | 2.97619048 | 2385.714286 | 4.9702381 | 2500 | 5.20833334 |
General | 96-core 384 GB single-node | 2142.85714286 | 4.46428571 | 3578.571429 | 7.45535713 | 3750 | 7.8125 |
General | 128-core 512 GB single-node | 2857.14285714 | 5.95238095 | 4771.428571 | 9.94047618 | 5000 | 10.41666666 |
Instance Type | Compute Node Specifications | Beijing, Shanghai, Guangzhou, Chengdu, and Nanjing | Hong Kong (China) | Singapore, Virginia, São Paulo, and Frankfurt | |||
| | Yearly/Monthly Subscription Price (USD/Month) | Pay-as-You-Go Price (USD/Hour) | Yearly/Monthly Subscription Price (USD/Month) | Pay-as-You-Go Price (USD/Hour) | Yearly/Monthly Subscription Price (USD/Month) | Pay-as-You-Go Price (USD/Hour) |
General | 4-core 16 GB | 89.28571429 | 0.18571429 | 149.1071429 | 0.31014284 | 156.25 | 0.325 |
General | 8 cores and 32 GB | 178.5714286 | 0.37142857 | 298.2142857 | 0.62028571 | 312.5 | 0.65 |
General | 12-core 48 GB | 267.8571429 | 0.55714285 | 447.3214286 | 0.93042856 | 468.75 | 0.975 |
General | 16 cores and 64 GB | 357.1428571 | 0.74285714 | 596.4285714 | 1.24057142 | 625 | 1.3 |
General | 20-core 80 GB | 446.4285715 | 0.92857145 | 745.5357145 | 1.5507142 | 781.25 | 1.625 |
General | 24-core 96 GB | 535.7142857 | 1.11607143 | 894.6428571 | 1.86383928 | 937.5 | 1.953125 |
General | 28 cores and 112 GB | 625 | 1.3 | 1043.75 | 2.17099988 | 1093.75 | 2.275 |
General | 32 cores and 128 GB | 714.2857143 | 1.48809524 | 1192.857143 | 2.48511905 | 1250 | 2.60416667 |
General | 36-core 144 GB | 803.5714286 | 1.67142861 | 1341.964286 | 2.79128556 | 1406.25 | 2.925 |
General | 40-core 160 GB | 892.8571429 | 1.85714285 | 1491.071429 | 3.10142855 | 1562.5 | 3.25 |
General | 48-core 192 GB | 1071.428571 | 2.22857142 | 1789.285714 | 3.72171426 | 1875 | 3.9 |
General | 56-core 224 GB | 1250 | 2.6 | 2087.5 | 4.34199997 | 2187.5 | 4.55 |
General | 60-core 240 GB | 1339.285715 | 2.78571425 | 2236.607143 | 4.6521428 | 2343.75 | 4.875 |
General | 64 cores and 256 GB | 1428.571429 | 2.97619048 | 2385.714286 | 4.9702381 | 2500 | 5.20833334 |
General | 72-core 288 GB | 1607.142857 | 3.34714285 | 2683.928571 | 5.58972856 | 2812.5 | 5.8575 |
General | 80-core 320 GB | 1785.714286 | 3.7142857 | 2982.142857 | 6.2028571 | 3125 | 6.5 |
General | 84-core 336 GB | 1875 | 3.89999995 | 3131.25 | 6.51299992 | 3281.25 | 6.825 |
General | 96-core 384 GB | 2142.857143 | 4.46428571 | 3578.571429 | 7.45535713 | 3750 | 7.8125 |
General | 108-core 432 GB | 2410.714286 | 5.01428565 | 4025.892857 | 8.37385704 | 4218.75 | 8.775 |
General | 112-core 448 GB | 2500 | 5.19999998 | 4175 | 8.68399994 | 4375 | 9.1 |
General | 120-core 480 GB | 2678.571429 | 5.5714285 | 4473.214286 | 9.3042856 | 4687.5 | 9.75 |
General | 128-core 512 GB | 2857.142857 | 5.95238095 | 4771.428571 | 9.94047618 | 5000 | 10.41666666 |
General | 144-core 576 GB | 3214.285713 | 6.68571426 | 5367.857142 | 11.16514278 | 5625 | 11.7 |
General | 160-core 640 GB | 3571.428571 | 7.4285714 | 5964.285714 | 12.4057142 | 6250 | 13 |
General | 168-core 672 GB | 3750 | 7.81250001 | 6262.5 | 13.04687496 | 6562.5 | 13.67187502 |
General | 192-core 768 GB | 4285.714286 | 8.92714285 | 7157.142858 | 14.90832856 | 7500 | 15.6225 |
General | 216-core 864 GB | 4821.428571 | 10.04464287 | 8051.785714 | 16.77455352 | 8437.5 | 17.57812502 |
General | 224-core 896 GB | 5000 | 10.41666668 | 8350.000001 | 17.39583335 | 8750 | 18.22916669 |
General | 240-core 960 GB | 5357.142857 | 11.1428571 | 8946.428571 | 18.6085713 | 9375 | 19.5 |
General | 256-core 1024 GB | 5714.285714 | 11.9057142 | 9542.857142 | 19.88254286 | 10000 | 20.835 |
General | 288-core 1152 GB | 6428.571429 | 13.3928571 | 10735.71429 | 22.36607142 | 11250 | 23.4375 |
General | 320-core 1280 GB | 7142.857143 | 14.8809524 | 11928.57143 | 24.8511905 | 12500 | 26.0416667 |
General | 336-core 1344 GB | 7499.999999 | 15.6 | 12525 | 26.05199982 | 13125 | 27.3 |
General | 360-core 1440 GB | 8035.714285 | 16.73571425 | 13419.64286 | 27.9486428 | 14062.5 | 29.2875 |
General | 384-core 1536 GB | 8571.428571 | 17.8585714 | 14314.28571 | 29.82381429 | 15000 | 31.25249995 |
General | 432-core 1728 GB | 9642.857142 | 20.05714278 | 16103.57143 | 33.49542834 | 16875 | 35.1 |
General | 448-core 1792 GB | 10000 | 20.83333336 | 16700 | 34.7916667 | 17500 | 36.45833338 |
General | 480-core 1920 GB | 10714.28571 | 22.2857142 | 17892.85714 | 37.2171426 | 18750 | 39 |
General | 504-core 2016 GB | 11250 | 23.42999995 | 18787.5 | 39.12809992 | 19687.5 | 41.0025 |
General | 512-core 2048 GB | 11428.57143 | 23.80952384 | 19085.71429 | 39.7619048 | 20000 | 41.66666672 |
General | 576-core 2304 GB | 12857.14286 | 26.78571426 | 21471.42857 | 44.73214278 | 22500 | 46.875 |
General | 640-core 2560 GB | 14285.71429 | 29.7619048 | 23857.14286 | 49.702381 | 25000 | 52.0833334 |
General | 648-core 2592 GB | 14464.28571 | 30.12428565 | 24155.35714 | 50.30755704 | 25312.5 | 52.7175 |
General | 672-core 2688 GB | 15000 | 31.24999997 | 25050 | 52.18749991 | 26250 | 54.6875 |
General | 720-core 2880 GB | 16071.42857 | 33.4285713 | 26839.28571 | 55.8257139 | 28125 | 58.5 |
General | 768-core 3072 GB | 17142.85714 | 35.71428568 | 28628.57143 | 59.64285704 | 30000 | 62.5 |
General | 864-core 3456 GB | 19285.71429 | 40.17857139 | 32207.14286 | 67.09821417 | 33750 | 70.3125 |
General | 896-core 3584 GB | 20000 | 41.66666665 | 33400 | 69.58333326 | 35000 | 72.91666664 |
General | 960-core 3840 GB | 21428.57143 | 44.6428571 | 35785.71429 | 74.5535713 | 37500 | 78.125 |
General | 1024-core 4096 GB | 22857.14286 | 47.6190476 | 38171.42857 | 79.52380944 | 40000 | 83.3333333 |
General | 1152-core 4608 GB | 25714.28572 | 53.5714284 | 42942.85716 | 89.46428568 | 45000 | 93.75 |
General | 1280-core 5120 GB | 28571.42857 | 59.528571 | 47714.28571 | 99.4127143 | 50000 | 104.175 |
Storage Space Pricing of Read-Only Analysis Engine
Whether in single-node or multi-node mode, the unit price of storage space for the read-only analysis engine remains unchanged.
Beijing, Shanghai, Guangzhou, Chengdu, and Nanjing | Hong Kong (China) | Singapore, Virginia, São Paulo, and Frankfurt | |||
Monthly Subscription (USD/GB/Month) | Pay-as-You-Go (USD/GB/Hour) | Monthly Subscription (USD/GB/Month) | Pay-as-You-Go (USD/GB/Hour) | Monthly Subscription (USD/GB/Month) | Pay-as-You-Go (USD/GB/Hour) |
0.282 | 0.00039167 | 0.3384 | 0.000514 | 0.2286 | 0.000413 |
Value-Added Services Pricing Description
SQL Insight (Database Audit) Price
SQL Insight (Database Audit) records database access and SQL statement execution, helping enterprises implement risk control and enhance data security levels. You are charged for this feature only after enabling SQL Insight (Database Audit). The pricing is as shown in the table below. For more details, visit SQL Insight (Database Audit) Billing Instructions.
Region | Price (USD/GB/Hour) | |
| Standard Storage | STANDARD_IA Storage |
China (including financial regions) | 0.00147059 | 0.00018382 |
Countries and Regions Outside China | 0.00220588 | 0.00027573 |
Database Proxies Pricing
Database proxies, positioned between the TencentDB service and application services, proxy all requests from application services to access the database. Database proxies are billed on a pay-as-you-go basis, with the billing unit being CU. The pricing for database proxies varies by region, as detailed in the table below. For more information, visit Database Proxy Commercial Billing and Activity Instructions.
Note:
CU refers to the minimum billing specification of a database proxy (that is, the price of a 2-core 4000MB memory proxy specification). Currently, database proxy nodes come in three specifications: 2-core 4000MB, 4-core 8000MB, and 8-core 16000MB, corresponding to 1 CU, 2 CU, and 4 CU respectively.
Region | Price (USD/CU/Hour) |
Shanghai, Nanjing, Chongqing, Chengdu, Guangzhou, Beijing | 0.06865672 |
Hong Kong (China) | 0.11492537 |
Jakarta, Virginia, Bangkok, Tokyo, Singapore, Seoul, Frankfurt, Silicon Valley, Sao Paulo | 0.11791045 |
Shenzhen Finance, Shanghai Finance, and Beijing Finance | 0.11641791 |
Note:
The regions displayed above are all the regions where the current instance supports deployment. Some regions do not currently support enabling the database proxy feature. The regions that support enabling are: Beijing, Shanghai, Guangzhou, Shanghai Finance, Beijing Finance, Chengdu, Chongqing, Nanjing, Hong Kong (China), Tokyo, Bangkok, Virginia, Silicon Valley, Seoul, Singapore.
CPU Elastic Scale-out Price
The elastic CPU expansion feature can better alleviate performance pressure caused by sudden requests, adapt to peak business traffic, and ensure the stability of online businesses. It also supports CPU scale-in during periods of decreased traffic to avoid resource waste. The specific billing formula and price are as follows. For more detailed information, visit Billing Instructions.
Billing Formula
The CPU elastic scale-out feature is charged in pay-as-you-go mode. It is charged by the minute, and the fee is deducted once per hour.
Billing formula = (Single-core fee x Added CPU cores) x Scale-out duration (minutes)/60.
Single-Core Fee
Region | Unit Price (USD/Core/Hour) |
Chengdu and Chongqing | 0.03 |
Guangzhou, Shanghai, Beijing, and Nanjing | 0.04 |
Hong Kong (China), Tokyo, Seoul, and Bangkok | 0.0495 |
Frankfurt and São Paulo | 0.0365 |
Singapore, Jakarta, Silicon Valley, Virginia, and Riyadh | 0.061 |
Region | Unit Price (USD/Core/Hour) |
Chengdu and Chongqing | 0.06 |
Guangzhou, Shanghai, Beijing, and Nanjing | 0.08 |
Hong Kong (China), Tokyo, Seoul, and Bangkok | 0.099 |
Frankfurt and São Paulo | 0.073 |
Singapore, Jakarta, Silicon Valley, Virginia, and Riyadh | 0.122 |
Region | Unit Price (USD/Core/Hour) |
Chengdu and Chongqing | 0.09 |
Guangzhou, Shanghai, Beijing, and Nanjing | 0.12 |
Hong Kong (China), Tokyo, Seoul, and Bangkok | 0.1485 |
Frankfurt and São Paulo | 0.1095 |
Singapore, Jakarta, Silicon Valley, Virginia, and Riyadh | 0.183 |
Billing Examples
Note:
The following price cases are for reference only. Actual prices may vary by factors such as regions, promotion, and policies. See the official website for the latest price.
For example, if you are in the Guangzhou region:
Purchase of a yearly/monthly subscription TencentDB for MySQL (two-node) in Guangzhou Zone 3, with 4-core, 8000MB memory and 500GB disk, for a duration of 1 month.
Purchase one yearly/monthly subscription TencentDB for MySQL (two-node) in Guangzhou Zone 4, with 4-core, 8000MB memory and 200GB disk, for a duration of 1 month.
Total cost = Memory and CPU cost + Storage space cost + Backup space cost
Memory specification fees
The monthly price for a 4-core, 8000MB instance in the Guangzhou region is USD 120/month. Memory specification fee = 2 × USD 120/month × 1 month = USD 240.
Storage space fees
In the Guangzhou region, the monthly price for instance disk is 0.10588 USD/GB/month. Storage space cost = (500GB + 200GB) × 0.10588 USD/GB/month × 1 month = 74.116 USD.
Backup space fees
For High Availability Edition instances running in Guangzhou Zone 3, the purchased database storage space is 500GB per month; for those in Guangzhou Zone 4, it is 200GB per month. Then, the Guangzhou region will have 700GB of free backup space per month.
Once the total backup storage space in the Guangzhou region exceeds 700GB, for example, when data backup reaches 800GB and log backup reaches 100GB, the billable space would be 800 + 100 - 700 = 200GB. For the current hour, you will be charged for this additional 200GB of exceeding backup space, and subsequent exceeding backup space will be billed accordingly.
Backup space cost (hourly) = 200GB (exceeding backup space, which may vary in actual scenarios) × 0.000113 USD/GB/hour.
FAQs
Why are there additional charges for my instance under the yearly/monthly subscription billing mode?
Please confirm whether your backup space exceeds the free quota. Backup space exceeding the free quota will be charged.
Backup space usage can be viewed on the database backup page in the MySQL console. For details about backup space billing, see Backup Space Billing.
Are Pay-as-you-go instances charged when not in use?
Pay-as-you-go instances will be billed continuously. Please terminate it promptly when the instance is no longer in use to avoid further charges.
What files are stored in the storage space?
Data files: the space occupied by data, including created tables, indexes, and so on.
System files: including shared tablespaces, error log files, REDO LOG, UNDO LOG, and data dictionary, which are essential for the system.
binlog files: record all DDL and DML statements (except data query statements such as select, show, and so on). The primary purpose of binlog is replication and recovery. The more data changes, the more binlog is generated. The generated binlog files will be uploaded to COS, thus freeing up local binlog storage space.
Documentation
TencentDB for MySQL supports purchasing instances via the console and APIs. See Purchase Methods.
TencentDB for MySQL will send alert messages to users from before expiration until resource release. See Overdue Payments.
TencentDB for MySQL supports requesting refunds via the console. See Refund Instructions.
TencentDB for MySQL supports switching billing modes. See Switching from Pay-as-You-Go to Yearly/Monthly Subscription.
TencentDB for MySQL supports upgrading or downgrading instance specifications. See Instance Adjustment Fees.
Help and Support
Was this page helpful?
You can also Contact sales or Submit a Ticket for help.
Help us improve! Rate your documentation experience in 5 mins.
Feedback