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
Storage Resource Pack
Last updated: 2025-01-13 10:00:02
The storage resource pack is a prepaid resource type in TDSQL-C for MySQL, which can be used to deduct the storage resources used by the serverless instance. This document describes the specification types and prices of storage resource packs.
Specification Types and Prices
Specification Type | Applicable Scope of Storage Capacity | Unit Price in Chinese Mainland (USD/TB) | Unit Price Outside Chinese Mainland (USD/TB) |
Basic Edition | 2–200TB (200 exclusive) | 6-month validity period: 0.2568 1-year validity period: 0.271 | 6-month validity period: 0.2806 1-year validity period: 0.2962 |
General Edition | 200–2000 TB (2000 exclusive) | 6-month validity period: 0.2425 1-year validity period: 0.2568 | 6-month validity period: 0.265 1-year validity period: 0.2806 |
Enterprise Edition | 2000–20,000 TB (20,000 exclusive) | 6-month validity period: 0.2282 1-year validity period: 0.2425 | 6-month validity period: 0.2494 1-year validity period: 0.265 |
Case
We will compare the storage resource fees of two instances (one without a storage resource package and the other with a storage resource package) to more intuitively understand the cost difference between using and not using a storage resource package.
Case background
Region: Beijing.
Instance Mode: Single-Node Edition.
The first instance: Unused storage resource package will be billed on a pay-as-you-go basis, denoted as Instance A.
The second instance: Utilizing the storage resource package, a Basic Edition storage resource package was purchased and bound, offering a storage capacity of 10TB with a validity period of 6 months. Denoted as Instance B.
Operation scenario: Instance A and instance B have been running continuously for 3 hours respectively. The storage space used in the first hour is 0.5TB, the storage space used in the second hour is 1TB, and the storage space used in the third hour is 2TB. The storage resource costs of these 3 hours are calculated and compared below.
Cost comparison
Comparative item | Instance A (Unused storage resource package) | Instance B (Used storage resource package) |
Billing formula | storage space fees = storage space price × storage space total storage resource fees of running for 3 hours = fees for the first hour + fees for the second hour + fees for the third hour | storage space fees = storage space price × storage space total storage resource fees of running for 3 hours = fees for the first hour + fees for the second hour + fees for the third hour |
Billing model | pay as you go | storage resource pack |
Storage space fees (unit price) | 0.00072 USD per GB Approximately equal to 0.72 USD per TB | 0.2568 USD per TB |
Storage space | the storage space used in the first hour: 0.5TB the storage space used in the second hour: 1TB the storage space used in the third hour: 2TB | the storage space used in the first hour: 0.5TB the storage space used in the second hour: 1TB the storage space used in the third hour: 2TB |
Storage resource fees | 0.72 x 0.5 + 0.72 x 1 + 0.72 x 2 = 2.52 USD | 0.2568 x 0.5 + 0.2568 x 1 + 0.2568 x 2 = 0.8988 USD |
Subsequent billing | subsequent operations of instance A will continue to use pay-as-you-go billing, resulting in new fees | the total storage resource package purchased by instance B is 10TB. In the past 3 hours, 3.5TB has been consumed, and the remaining amount is 6.5TB. This storage resource package will continue to be consumed in the future. Instance B will not be restored until the storage resource package is consumed or expires. For pay-as-you-go billing, you can also continue to purchase and bind other storage resource packages before the storage resource package is consumed. |
Compare results
It can be seen from the above comparison that since the unit price of storage space in a storage resource package is lower than that of pay-as-you-go, the overall storage resource fees is reduced, and it is more favorable to use a storage resource package. The unit prices of storage resource packages for Basic Edition, General Edition, and Enterprise Edition are different. You can choose the appropriate specification type based on the actual storage required.
Note
Storage resource packages will accumulate the actual storage usage on an hourly basis for deduction, 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 storage 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:
Storage 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 storage resource pack can be shared by multiple serverless clusters.
A serverless cluster can be bound to a maximum of ten storage resource packages, with support for adjusting the consumption priority order of multiple storage resource packages. The cluster will consume resources in ascending order based on the priority level numbers.
Storage resource packages will accumulate the consumption on an hourly basis for deduction.
Storage resource packages do not support downgrade once purchased.
Management
Refund
For resource packages that remain unused within their validity period, each Tencent Cloud account (primary account) is calculated on a calendar year basis, with a maximum of 20 refundable resource packages per year. As for resource packages that have expired or been fully utilized, refunds are currently not supported. For detailed refund instructions, see Requesting Refund for Resource Pack.
Note：
Regarding the limitation 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 refreshes on July 1 at 00:00:00 every year, thus 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
Was this page helpful?
You can also Contact Sales or Submit a Ticket for help.
Yes
No