This document introduces the billing details for TencentDB for MySQL storage overusage.
Overview
TencentDB for MySQL is categorized into local disk instances and cloud disk instances based on the type of storage. Local disk instances adopt a compute-storage integrated architecture, where computing and storage resources are deployed on the same physical node. Under this architecture, the disk capacity of a node is limited by the physical hardware specifications, resulting in a definite capacity ceiling. Once overusage reaches the host's limit, overall service quality and stability will be affected.
Note:
Users with high storage demands are recommended to use the cloud disk edition. Currently, the cloud disk edition supports up to 32 TB of storage. The console provides a one-click migration capability to migrate local disk instances to cloud disk edition instances. Effective Time
The billing for storage overusage takes effect starting from 00:00:00, August 1, 2026, Beijing Time.
Target Audience
This document applies to local disk instances.
In the early stage, to lower the user adoption barrier, local disk instances were not immediately locked or had writes restricted after data files exceeded the purchased specifications. This resulted in the actual disk usage of some existing instances remaining above the purchased specifications for an extended period. The current policy is as follows:
New instances: For instances that newly exceed their purchased specifications after the effective date, a disk pre-lock event will be triggered (read/write operations are allowed at this stage). After 24 hours, a lock event will be triggered (only read operations are allowed). Storage overusage billing will be incurred for the portion of the instance's total used storage space that exceeds the purchased storage space.
Existing instances: For existing instances that have already exceeded their purchased specifications before the effective date, Tencent Cloud will continue to allow read and write operations. However, storage overusage billing will be incurred for the portion that exceeds the purchased specifications. Please note that when an existing overusage instance reaches the host's storage space risk threshold, a disk pre-lock event will be triggered (read/write operations are allowed at this stage). After 24 hours, a lock event will be triggered (only read operations are allowed).
Billing Rules
Billing Objects
This billing applies to instances that simultaneously meet all of the following conditions:
1. The instance's disk type is local disk (Local SSD).
2. The instance's current actual total usage exceeds the purchased storage space specification.
Billing Formula
Overusage cost = (Actual total usage - Purchased storage space) × Overusage unit price × Usage duration.
Overage Unit Price
Three-Node General/Dedicated Local Disks
Two-Node General/Dedicated Local Disks
General/Dedicated Local Disk Read-Only Instances
|
Shanghai, Nanjing, Chongqing, Chengdu, Beijing, Guangzhou | 0.000662 |
Hong Kong (China), Singapore, Tokyo, Osaka, Jakarta, Bangkok, and Seoul | 0.000882 |
Virginia, Silicon Valley, Frankfurt, Sao Paulo, and Riyadh | 0.001103 |
|
Shanghai, Nanjing, Chongqing, Chengdu, Beijing, Guangzhou | 0.000441 |
Hong Kong (China), Singapore, Tokyo, Osaka, Jakarta, Bangkok, and Seoul | 0.000588 |
Virginia, Silicon Valley, Frankfurt, Sao Paulo, and Riyadh | 0.000735 |
|
Shanghai, Nanjing, Chongqing, Chengdu, Beijing, Guangzhou | 0.000221 |
Hong Kong (China), Singapore, Tokyo, Osaka, Jakarta, Bangkok, and Seoul | 0.000294 |
Virginia, Silicon Valley, Frankfurt, Sao Paulo, and Riyadh | 0.000368 |
Note:
For specific unit prices, see the official pricing page at the time the billing takes effect. The overusage billing unit price aligns with the price for scaling out disks of the same specification, with no additional charges. Billing method
The overusage portion is settled in the pay-as-you-go (postpaid) mode. It is billed hourly based on the actual overusage amount and usage duration. For usage periods shorter than one hour, billing is based on the actual storage overusage time. Bills are generated daily.
Overusage fees will be displayed as an independent billing item in the cost bill for easy identification and management.
Recommended Actions
To avoid incurring additional charges, you are advised to take the following measures as soon as possible:
1. Scaling Out Storage Specifications
2. Cleaning Up Redundant Data
Check and clean up unused big tables, historical archive data, redundant indexes, and other items to reduce data file occupancy.
3. Migrating to a Cloud Disk Instance
If your business is expected to grow continuously, you are advised to migrate to a cloud disk edition instance. The cloud disk supports elastic scaling out and has no physical node capacity restrictions. For the operation, see One-Click Migration. 4. Setting Up Disk Alarms
Configure a disk utilization alarm (recommended threshold: 85%) to promptly detect capacity changes. For the operation, see the alarm policy. Viewing Overusage
Method for Determination: Check the Used Space and Storage Specification of each instance. If the used space exceeds the storage specification, the instance is in an overusage state.