TDSQL-C for MySQL
- Release Notes and Announcements
- Announcements
- Product Introduction
- Suggestions on Usage Specifications
- Kernel Features
- Kernel Version Release Notes
- Optimized Kernel Version
- Functionality Features
- Performance Features
- Security Features
- Stability Feature
- Analysis Engine Features
- Purchase Guide
- Value-Added Services Billing Overview
- Database Audit
- Audit Rule Template
- Serverless Service
- Serverless Introduction
- Serverless Resource Pack
- Configuration Change
- Operation Guide
- Database Connection
- Configuring Network Address
- Instance Management
- Configuration Adjustment
- Instance Mode Management
- Cluster Management
- Scaling Instance
- Database Proxy
- Database Proxy Kernel Features
- Managing Database Proxy
- Automatic Read/Write Separation
- Connection Pool Feature
- Other Features
- Account Management
- Console Account
- Database Account
- Configuring Custom Password Strength
- Database Management
- Database Management Tool
- Columnar Storage Index (CSI)
- Utilization of Columnar Storage Indexes
- Read-Only Analysis Engine
- Feature Limits and Compatibility
- Description of Functions and Operators
- Read-Only Analysis Engine Management
- Data Loading
- Executing Queries
- Exclusive Features
- Performance Optimization
- Performance White Paper
- Parameter Configuration
- Multi-AZ Deployment
- Backup and Restoration
- Performing Backup
- Managing Backup
- Rollback
- Restoring Data from Logical Backups
- Restoring Data Through the Console
- Restoring Data from Snapshot Backup
- Data Migration
- Parallel Query
- Setting Parallel Query
- Database Security and Encryption
- Access and Authorization
- Security Group Management
- TencentDB Security Group Management
- Monitoring and Alarms
- Monitoring
- Alarms
- Monitoring Metric Alarm
- Practical Tutorial
- Data Rollback
- Database/Table-Level Rollback
- Rolling back Entire Cluster
- White Paper
- Security White Paper
- Performance White Paper
- Troubleshooting
- Connection Issues
- API Documentation
- Making API Requests
- Instance APIs
- Account APIs
- Audit APIs
- Database Proxy APIs
- Backup and Restoration APIs
- Parameter Management APIs
- Performance Analysis APIs
- Serverless APIs
- ResourcePackage APIs
- Other APIs
- FAQs
- Service Agreement
- TDSQL-C Policy
- General References
Billing Overview
Last updated: 2024-12-31 17:24:26
This document describes the pricing of TDSQL-C for MySQL Serverless.
Billing Mode
In the serverless mode, computing and storage are billed separately: computing is billed by the number of CCUs, while storage is billed by the usage in GB. The billing system calculates the usage by second and settles fees by hour.
Billing Formula
Total serverless fees = compute node fees + storage space fees = serverless computing power price number of CCUs + storage space price storage space
Serverless Computing Power Pricing
Billing Unit | CCU Pay-per-Use Pricing (USD/unit/second) | |
| Supported regions: Guangzhou, Shanghai, Beijing, and Nanjing Regions to be supported: Chengdu and Chongqing | Supported regions: Hong Kong (China), Singapore, Silicon Valley, and Virginia Regions to be supported: Frankfurt |
Serverless Instances | 0.00001397 | 0.00001529 |
Note:
TDSQL-C Compute Unit (CCU) is the computing and billing unit for the Serverless Edition. 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.
You can refer to Compute Unit to select the corresponding maximum and minimum CCU values. The upper limits of storage space vary for different compute units. For details, refer to Compute Unit.
Storage Space Pricing
Serverless service edition cluster storage space is billed on a pay-as-you-go basis. In Guangzhou, Shanghai, Beijing, Nanjing, Chengdu, and Chongqing, the price is USD0.00072/GB/hour, while in Hong Kong (China), Singapore, Silicon Valley, Virginia, Seoul, Tokyo, and Frankfurt, the price is USD0.000792/GB/hour.
Serverless Resource Package Overview
TDSQL-C for MySQL has launched the resource package service, allowing for the advance purchase of compute and Storage resources at lower unit prices, achieving cost savings. The following will introduce the definition and billing sequence of the resource package.
A resource package is a type of prepaid resource, divided into compute resource packages and storage resource packages. They can be used to offset the compute or Storage resources generated by a Serverless service edition cluster. After a user purchases and binds a resource package to a cluster, it will first consume the compute or storage resources from the resource package. When the resources are fully consumed within the validity period, you can purchase a new resource package and continue to bind it for use. If no new resource package is bound for deduction, the cluster will switch to a pay-as-you-go billing method. At that time, the fees incurred by using the cluster will be deducted from your Tencent Cloud account balance.
Note:
For easier understanding, you can compare the resource package to a mobile data plan package. Suppose the normal price for mobile data is USD1/GB, and a user spends USD10 to buy a 50 GB mobile data plan for one month at USD0.2/GB. Thus, the user can enjoy the discounted unit price of USD0.2/GB during the one-month validity period. Once the data plan is used up within the validity period, the user can continue to purchase new mobile data plan packages to enjoy the discounted price. If the user does not purchase and use new mobile data plan packages, the fees of data will revert to USD1/GB.
Was this page helpful?
You can also Contact Sales or Submit a Ticket for help.
Yes
No