tencent cloud

TDSQL-C for MySQL

Release Notes and Announcements
Release Notes
Product Announcements
Beginner's Guide
Product Introduction
Overview
Strengths
Use Cases
Architecture
Product Specifications
Instance Types
Product Feature List
Database Versions
Regions and AZs
Common Concepts
Use Limits
Suggestions on Usage Specifications
Kernel Features
Kernel Overview
Kernel Version Release Notes
Optimized Kernel Version
Functionality Features
Performance Features
Security Features
Stability Feature
Analysis Engine Features
Inspection and Repair of Kernel Issues
Purchase Guide
Billing Overview
Product Pricing
Creating Cluster
Specification Adjustment Description
Renewal
Payment Overdue
Refund
Change from Pay-as-You-Go to Yearly/Monthly Subscription
Change from Pay-as-You-Go to Serverless Billing
Value-Added Services Billing Overview
Viewing Billing Statements
Getting Started
Database Audit
Overview
Viewing Audit Instance List
Enabling Audit Service
Viewing Audit Logs
Log Shipping
Post-Event Alarm Configuration
Modifying Audit Rule
Modifying Audit Service
Disabling Audit Service
Audit Rule Template
Viewing Audit Task
Authorizing Sub-User to Use Database Audit
Serverless Service
Serverless Introduction
Creating and Managing a Serverless Cluster
Elastic Scaling Management Tool
Serverless Resource Pack
Multi-AZ Deployment
Configuration Change
FAQs
Serverless Cost Estimator
Operation Guide
Operation Overview
Switching Cluster Page View in Console
Database Connection
Instance Management
Configuration Adjustment
Instance Mode Management
Cluster Management
Scaling Instance
Database Proxy
Account Management
Database Management
Database Management Tool
Parameter Configuration
Multi-AZ Deployment
GD
Backup and Restoration
Operation Log
Data Migration
Parallel Query
Columnar Storage Index (CSI)
Analysis Engine
Database Security and Encryption
Monitoring and Alarms
Basic SQL Operations
Connecting to TDSQL-C for MySQL Through SCF
Tag
Practical Tutorial
Classified Protection Practice for Database Audit of TDSQL-C for MySQL
Upgrading Database Version from MySQL 5.7 to 8.0 Through DTS
Usage Instructions for TDSQL-C MySQL
New Version of Console
Implementing Multiple RO Groups with Multiple Database Proxy Connection Addresses
Strengths of Database Proxy
Selecting Billing Mode for Storage Space
Creating Remote Disaster Recovery by DTS
Creating VPC for Cluster
Data Rollback
Solution to High CPU Utilization
How to Authorize Sub-Users to View Monitoring Data
White Paper
Security White Paper
Performance White Paper
Troubleshooting
Connection Issues
Performance Issues
API Documentation
History
Introduction
API Category
Making API Requests
Instance APIs
Multi-Availability Zone APIs
Other APIs
Audit APIs
Database Proxy APIs
Backup and Recovery APIs
Parameter Management APIs
Billing APIs
serverless APIs
Resource Package APIs
Account APIs
Performance Analysis APIs
Data Types
Error Codes
FAQs
Basic Concepts
Purchase and Billing
Compatibility and Format
Connection and Network
Features
Console Operations
Database and Table
Performance and Log
Database Audit
Between TDSQL-C for MySQL and TencentDB for MySQL
Service Agreement
Service Level Agreement
Terms of Service
TDSQL-C Policy
Privacy Policy
Data Privacy and Security Agreement
General References
Standards and Certifications
Glossary
Contact Us

Resource Pack Overview

PDF
Focus Mode
Font Size
Last updated: 2026-03-24 16:28:39
In TDSQL-C for MySQL, there are two different types of prepaid resource packs: compute resource packs and storage resource packs, which can be used to deduct the storage and compute resources used by the serverless cluster. By purchasing resource packs, you can reserve resources in advance. Compared to the pay-as-you-go option, the resource packs can help you save more costs. It is more cost-effective to purchase larger capacity and longer validity period.

Resource Pack Description

Prepaid Resource Pack
Compute Resource Pack
Storage Resource Pack
Deduction object
The compute resource pack will be used preferably for the deduction of actual compute resources used by its bound serverless cluster. When the pack is used up, the resource usage will be pay-as-you-go.
The storage resource pack will be used preferably for the deduction of actual storage resources used by its bound serverless cluster. When the pack is used up, the resource usage will be pay-as-you-go.
Deduction rules
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 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.
The storage resource pack will be deducted based on the actual storage used per hour, 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 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.
Renewal
Not supported

Batch Binding Resource Packs
Up to 10 compute resource packs can be bound to a single cluster at a time.
Up to 10 storage resource packs can be bound to a single cluster at a time.
Consumption priority
When a cluster is bound to multiple resource packs, the system automatically sets the consumption priority sequence based on the order of binding. It also supports manually adjustment of consumption priority order. The resources are consumed according to the consumption priority level (1 to 10), from the lowest to the highest.
Note:
The consumption priorities of compute resource packs and storage resource packs are set separately, and the set priorities are only effective for the same type of resource pack. For example, if a cluster is bound with two compute resource packs, and their consumption priorities are set as 1 and 2 respectively, then the compute resource pack with a priority level of 1 will be consumed first.
The consumption priority of the resource pack that is bound by default is set to 1, with subsequent priorities assigned in ascending order.
Upon the depletion or expiration of a resource pack, the priority ranking for the consumption of the corresponding resource pack will be annulled.
Deduction period
The compute resource pack will be deducted based on the actual accumulated usage per second.
The storage resource pack will be deducted based on the actual average usage per hour.
Validity period
It is valid for 6 months (180 days) or 1 year (365 days) and can’t be used any longer once expired.
It is valid for 6 months (180 days) or 1 year (365 days) and can’t be used any longer once expired.
Region
It is available in or out of the Chinese mainland.
It is available in or out of the Chinese mainland.
Use Instructions

Available Region

In Chinese Mainland
Outside Chinese Mainland
Guangzhou, Nanjing, Shanghai, Beijing, Chengdu, Chongqing, Beijing Finance, Shanghai Finance
Hong Kong (China), Singapore, Seoul, Tokyo, Silicon Valley, Virginia, Frankfurt

Billing Mode

Serverless clusters offer the following four billing modes for you to choose flexibly. If you choose the fourth mode of resource pack for both compute and storage, you can enjoy a more favorable price than the yearly/monthly subscription option.
Pay-as-you-go for compute + resource pack for storage
Resource pack for compute + pay-as-you-go for storage
Pay-as-you-go for both compute and storage
Resource pack for both compute and storage
For more information, see Compute Resource Pack and Storage Resource Pack.

Related APIs

API
Description
This API (DescribeResourcePackageList) is used to query resource pack list.

Help and Support

Was this page helpful?

Help us improve! Rate your documentation experience in 5 mins.

Feedback