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
DocumentationTDSQL-C for MySQLRelease Notes and AnnouncementsAnnouncementsAnnouncement on Optimization of Instance Storage Capacity, IOPS, and I/O Bandwidth
Announcement on Optimization of Instance Storage Capacity, IOPS, and I/O Bandwidth
Last updated: 2024-10-10 10:12:27
Announcement on Optimization of Instance Storage Capacity, IOPS, and I/O Bandwidth
Last updated: 2024-10-10 10:12:27
Dear Tencent Cloud user, to provide you with a better performance experience, starting from October 12, 2024, TDSQL-C for MySQL will optimize the maximum storage capacity, maximum Input/Output Operations Per Second (IOPS), and I/O bandwidth for each instance specification through technical upgrade. Please pay attention to the changes in the instance specifications of your clusters.
Notes
This optimization of instance specification limits will not affect the continuity and stability of current network business.
This optimization of instance specification limits will apply to both existing and newly purchased instances.
After this optimization of instance specification limits is completed, for clusters using the pay-as-you-go storage billing mode, the value of the metric Storage Utilization Rate (%) may change due to the change in the storage limit. However, this change is normal, and the actual current storage capacity of an instance will not be affected. The specific reasons are as follows:
Since Storage utilization rate (%) = (Storage usage/Maximum storage capacity) x 100%, when the maximum storage capacity changes but storage usage remains the same, the storage utilization rate will also change (increase or decrease).
After this optimization, the monitoring chart for Storage Usage will remain unchanged, as illustrated below.
After this optimization, the monitoring chart for Storage Utilization Rate will change, as illustrated below.
Time to Take Effect
Starting from Saturday, October 12, 2024, Beijing Time (UTC+8).
Instance Specification Limit Change Information
1. Maximum Storage Capacity
When an instance is a preset resource, the changes are as follows.
Instance Type | Specification | Maximum storage capacity (TB) | |
| | Before optimization | After optimization |
General | 1-core, 1 GB | 3 | 100 |
| 1-core, 2 GB | 3 | 100 |
| 2-core, 4 GB | 10 | 100 |
| 2-core, 8 GB | 10 | 100 |
| 2-core, 16 GB | 30 | 100 |
| 4-core, 8 GB | 30 | 100 |
| 4-core, 16 GB | 30 | 100 |
| 4-core, 24 GB | 30 | 100 |
| 4-core, 32 GB | 30 | 100 |
| 8-core, 16 GB | 50 | 100 |
| 8-core, 32 GB | 50 | 100 |
| 8-core, 48 GB | 50 | 100 |
| 8-core, 64 GB | 50 | 100 |
| 12-core, 48 GB | 80 | 100 |
| 12-core, 72 GB | 80 | 100 |
| 12-core, 96 GB | 80 | 100 |
| 16-core, 64 GB | 100 | 100 |
| 16-core, 96 GB | 100 | 100 |
| 16-core, 128 GB | 150 | 100 |
Dedicated | 2-core, 4 GB | 10 | 156 |
| 2-core, 8 GB | 10 | 156 |
| 2-core, 16 GB | 30 | 156 |
| 4-core, 8 GB | 30 | 156 |
| 4-core, 16 GB | 30 | 156 |
| 4-core, 24 GB | 30 | 156 |
| 4-core, 32 GB | 30 | 156 |
| 8-core, 16 GB | 50 | 156 |
| 8-core, 32 GB | 50 | 156 |
| 8-core, 48 GB | 50 | 192 |
| 8-core, 64 GB | 50 | 192 |
| 12-core, 48 GB | 80 | 192 |
| 12-core, 72 GB | 80 | 192 |
| 12-core, 96 GB | 80 | 192 |
| 16-core, 32 GB | 100 | 192 |
| 16-core, 64 GB | 100 | 192 |
| 16-core, 96 GB | 100 | 256 |
| 16-core, 128 GB | 150 | 256 |
| 24-core, 96 GB | 150 | 256 |
| 24-core, 144 GB | 150 | 256 |
| 24-core, 192 GB | 150 | 256 |
| 32-core, 128 GB | 200 | 256 |
| 32-core, 192 GB | 200 | 384 |
| 32-core, 256 GB | 200 | 384 |
| 48-core, 192 GB | 300 | 384 |
| 48-core, 288 GB | 300 | 384 |
| 48-core, 384 GB | 300 | 384 |
| 48-core, 488 GB | 300 | 384 |
| 64-core, 256 GB | 400 | 384 |
| 64-core, 384 GB | 400 | 448 |
| 64-core, 512 GB | 400 | 448 |
| 88-core, 352 GB | 400 | 448 |
| 88-core, 710 GB | 400 | 448 |
When an instance is Serverless, the changes are as follows.
Maximum Computing Power Configuration (CCU) | Maximum Storage Capacity (TB) | |
| Before optimization | After optimization |
0.5 | 1 | 100 |
1 | 1 | 100 |
2 | 5 | 156 |
4 | 10 | 156 |
8 | 10 | 156 |
16 | 20 | 192 |
32 | 30 | 256 |
64 | 40 | 384 |
2. Maximum IOPS
When an instance is a preset resource, the changes are as follows.
Instance type | Specification | Maximum IOPS | |
| | Before optimization | After optimization |
General | 1-core, 1 GB | 8000 | 24000 |
| 1-core, 2 GB | 8000 | 24000 |
| 2-core, 4 GB | 48000 | 24000 |
| 2-core, 8 GB | 48000 | 36000 |
| 2-core, 16 GB | 48000 | 48000 |
| 4-core, 8 GB | 96000 | 96000 |
| 4-core, 16 GB | 96000 | 144000 |
| 4-core, 24 GB | 96000 | 160000 |
| 4-core, 32 GB | 96000 | 160000 |
| 8-core, 16 GB | 216000 | 160000 |
| 8-core, 32 GB | 216000 | 160000 |
| 8-core, 48 GB | 216000 | 180000 |
| 8-core, 64 GB | 216000 | 180000 |
| 12-core, 48 GB | 288000 | 160000 |
| 12-core, 72 GB | 288000 | 180000 |
| 12-core, 96 GB | 288000 | 240000 |
| 16-core, 64 GB | 384000 | 240000 |
| 16-core, 96 GB | 384000 | 360000 |
| 16-core, 128 GB | 384000 | 400000 |
Dedicated | 2-core, 4 GB | 48000 | 48000 |
| 2-core, 8 GB | 48000 | 72000 |
| 2-core, 16 GB | 48000 | 96000 |
| 4-core, 8 GB | 96000 | 144000 |
| 4-core, 16 GB | 96000 | 196000 |
| 4-core, 24 GB | 96000 | 216000 |
| 4-core, 32 GB | 96000 | 240000 |
| 8-core, 16 GB | 216000 | 320000 |
| 8-core, 32 GB | 216000 | 320000 |
| 8-core, 48 GB | 216000 | 400000 |
| 8-core, 64 GB | 216000 | 400000 |
| 12-core, 48 GB | 288000 | 360000 |
| 12-core, 72 GB | 288000 | 400000 |
| 12-core, 96 GB | 288000 | 480000 |
| 16-core, 32 GB | 384000 | 400000 |
| 16-core, 64 GB | 384000 | 480000 |
| 16-core, 96 GB | 384000 | 640000 |
| 16-core, 128 GB | 384000 | 640000 |
| 24-core, 96 GB | 480000 | 600000 |
| 24-core, 144 GB | 480000 | 640000 |
| 24-core, 192 GB | 480000 | 720000 |
| 32-core, 128 GB | 576000 | 600000 |
| 32-core, 192 GB | 576000 | 720000 |
| 32-core, 256 GB | 576000 | 960000 |
| 48-core, 192 GB | 648000 | 720000 |
| 48-core, 288 GB | 648000 | 720000 |
| 48-core, 384 GB | 648000 | 720000 |
| 48-core, 488 GB | 648000 | 960000 |
| 64-core, 256 GB | 720000 | 720000 |
| 64-core, 384 GB | 720000 | 960000 |
| 64-core, 512 GB | 720000 | 960000 |
| 88-core, 352 GB | 780000 | 960000 |
| 88-core, 710 GB | 780000 | 960000 |
When an instance is Serverless, the changes are as follows.
Maximum Computing Power Configuration (CCU) | Maximum IOPS | |
| Before optimization | After optimization |
0.5 | 24000 | 24000 |
1 | 24000 | 24000 |
2 | 24000 | 24000 |
4 | 96000 | 96000 |
8 | 216000 | 320000 |
16 | 384000 | 400000 |
32 | 576000 | 600000 |
64 | 720000 | 720000 |
3. I/O Bandwidth
When an instance is a preset resource, the changes are as follows.
Instance Type | Specification | I/O Bandwidth | |
| | Before optimization | After optimization |
General | 1-core, 1 GB | 1 Gbps | 3 Gbps |
| 1-core, 2 GB | 1 Gbps | 3 Gbps |
| 2-core, 4 GB | 6 Gbps | 3 Gbps |
| 2-core, 8 GB | 6 Gbps | 5 Gbps |
| 2-core, 16 GB | 6 Gbps | 6 Gbps |
| 4-core, 8 GB | 12 Gbps | 12 Gbps |
| 4-core, 16 GB | 12 Gbps | 18 Gbps |
| 4-core, 24 GB | 12 Gbps | 20 Gbps |
| 4-core, 32 GB | 12 Gbps | 20 Gbps |
| 8-core, 16 GB | 27 Gbps | 20 Gbps |
| 8-core, 32 GB | 27 Gbps | 20 Gbps |
| 8-core, 48 GB | 27 Gbps | 23 Gbps |
| 8-core, 64 GB | 27 Gbps | 23 Gbps |
| 12-core, 48 GB | 36 Gbps | 20 Gbps |
| 12-core, 72 GB | 36 Gbps | 23 Gbps |
| 12-core, 96 GB | 36 Gbps | 30 Gbps |
| 16-core, 64 GB | 48 Gbps | 30 Gbps |
| 16-core, 96 GB | 48 Gbps | 45 Gbps |
| 16-core, 128 GB | 48 Gbps | 50 Gbps |
Dedicated | 2-core, 4 GB | 6 Gbps | 6 Gbps |
| 2-core, 8 GB | 6 Gbps | 9 Gbps |
| 2-core, 16 GB | 6 Gbps | 12 Gbps |
| 4-core, 8 GB | 12 Gbps | 18 Gbps |
| 4-core, 16 GB | 12 Gbps | 25 Gbps |
| 4-core, 24 GB | 12 Gbps | 27 Gbps |
| 4-core, 32 GB | 12 Gbps | 30 Gbps |
| 8-core, 16 GB | 27 Gbps | 40 Gbps |
| 8-core, 32 GB | 27 Gbps | 40 Gbps |
| 8-core, 48 GB | 27 Gbps | 50 Gbps |
| 8-core, 64 GB | 27 Gbps | 50 Gbps |
| 12-core, 48 GB | 36 Gbps | 45 Gbps |
| 12-core, 72 GB | 36 Gbps | 50 Gbps |
| 12-core, 96 GB | 36 Gbps | 60 Gbps |
| 16-core, 32 GB | 48 Gbps | 50 Gbps |
| 16-core, 64 GB | 48 Gbps | 60 Gbps |
| 16-core, 96 GB | 48 Gbps | 80 Gbps |
| 16-core, 128 GB | 48 Gbps | 80 Gbps |
| 24-core, 96 GB | 60 Gbps | 75 Gbps |
| 24-core, 144 GB | 60 Gbps | 80 Gbps |
| 24-core, 192 GB | 60 Gbps | 90 Gbps |
| 32-core, 128 GB | 72 Gbps | 75 Gbps |
| 32-core, 192 GB | 72 Gbps | 90 Gbps |
| 32-core, 256 GB | 72 Gbps | 120 Gbps |
| 48-core, 192 GB | 81 Gbps | 90 Gbps |
| 48-core, 288 GB | 81 Gbps | 90 Gbps |
| 48-core, 384 GB | 81 Gbps | 90 Gbps |
| 48-core, 488 GB | 81 Gbps | 120 Gbps |
| 64-core, 256 GB | 90 Gbps | 90 Gbps |
| 64-core, 384 GB | 90 Gbps | 120 Gbps |
| 64-core, 512 GB | 90 Gbps | 120 Gbps |
| 88-core, 352 GB | 98 Gbps | 120 Gbps |
| 88-core, 710 GB | 98 Gbps | 120 Gbps |
When an instance is Serverless, the changes are as follows.
Maximum Computing Power Configuration (CCU) | I/O Bandwidth | |
| Before optimization | After optimization |
0.5 | 3 Gbps | 3 Gbps |
1 | 3 Gbps | 3 Gbps |
2 | 3 Gbps | 3 Gbps |
4 | 12 Gbps | 12 Gbps |
8 | 27 Gbps | 40 Gbps |
16 | 48 Gbps | 50 Gbps |
32 | 72 Gbps | 75 Gbps |
64 | 90 Gbps | 90 Gbps |
Was this page helpful?
You can also Contact Sales or Submit a Ticket for help.
Yes
No