TencentDB for MySQL
- Release Notes and Announcements
- Announcements
- Product Introduction
- Database Architecture
- Database Instance
- Kernel Features
- Kernel Version Release Notes
- Functionality Features
- Performance Features
- Parallel Query
- Security Features
- Stability Features
- Purchase Guide
- Getting Started
- Connecting to MySQL Instance
- Database Audit
- Audit Rule Template
- MySQL Cluster Edition
- Maintenance Management Instance
- Operation Guide
- Instance Management and Maintenance
- Instance Upgrade
- CPU Elastic Expansion
- Read-Only/Disaster Recovery Instances
- Database Proxy
- Database Proxy Kernel Features
- Database Proxy Management
- Automatic Read/Write Separation Feature
- Connection Pool Feature
- Other Features
- Account Management
- Database Management Center (DMC)
- Parameter Configuration
- Network and Security
- Backup and Rollback
- Restoring Database from Backup File
- Monitoring and Alarms
- Operation Logs
- Practical Tutorial
- Calling MySQL APIs in Python
- White Paper
- Performance White Paper
- Performance Test Report
- Troubleshooting
- Connections
- API Documentation
- Data Import APIs
- Rollback APIs
- Parameter APIs
- Making API Requests
- Instance APIs
- Database Proxy APIs
- Database Audit APIs
- Security APIs
- Account APIs
- Backup APIs
- Database APIs
- Monitoring APIs
- Log-related API
- FAQs
- Backup
- Connection and Login
- Instance Upgrade
- Performance and Memory
- Service Agreement
- Reference
DocumentationTencentDB for MySQLProduct IntroductionDatabase InstanceDatabase Instance Specification
Database Instance Specification
Last updated: 2024-08-16 10:03:26
This document introduces the instance specifications of TencentDB for MySQL, providing you with a comprehensive understanding of the supported specifications for MySQL instances. You may view this document for detailed configurations of each specification, or visit the purchase page to query the latest supported specifications.
Cluster Edition (Cloud Disk Edition)
For specifications of the Cluster Edition (cloud disk edition) instances, see this table.
Isolation Policy | CPU and Memory |
Standard Type | 2-core 4,000 MB |
| 2-core 8,000 MB |
| 2-core 16,000 MB |
| 4-core 8,000 MB |
| 4-core 16,000 MB |
| 4-core 32,000 MB |
| 8-core 16,000 MB |
| 8-core 32,000 MB |
| 8-core 64,000 MB |
| 16-core 32,000 MB |
| 16-core 64,000 MB |
| 16-core 128,000 MB |
Enhanced Type | 2-core 4,000 MB |
| 2-core 8,000 MB |
| 2-core 16,000 MB |
| 4-core 8,000 MB |
| 4-core 16,000 MB |
| 4-core 32,000 MB |
| 8-core 16,000 MB |
| 8-core 32,000 MB |
| 8-core 64,000 MB |
| 16-core 32,000 MB |
| 16-core 64,000 MB |
| 16-core 128,000 MB |
| 32-core 64,000 MB |
| 32-core 128,000 MB |
| 32-core 256,000 MB |
| 48-core 128,000 MB |
| 48-core 192,000 MB |
| 64-core 128,000 MB |
| 64-core 256,000 MB |
| 80-core 160,000 MB |
| 80-core 320,000 MB |
| 96-core 192,000 MB |
| 96-core 384,000 MB |
| 112-core 224,000 MB |
| 112-core 448,000 MB |
| 128-core 256,000 MB |
| 128-core 512,000 MB |
| 144-core 288,000 MB |
| 144-core 576,000 MB |
| 160-core 320,000 MB |
| 160-core 640,000 MB |
| 176-core 352,000 MB |
| 176-core 704,000 MB |
| 192-core 384,000 MB |
| 192-core 768,000 MB |
| 384-core 768,000 MB |
| 384-core 1,536,000 MB |
Two-node/Three-node (local SSD disk)
The following table lists the specifications of source instances (two-node/three-node), read-only instances, and disaster recovery instances.
Isolation Policy | CPU and Memory | Maximum IOPS | Storage Space |
General | 1-core 1000 MB | 1200 | 25GB - 3000GB |
| 1-core 2000 MB | 2000 | |
| 2-core 4000 MB | 4000 | |
| 4-core 8000 MB | 8000 | |
| 4-core 16000 MB | 14000 | 25GB - 4000GB |
| 8-core 16000 MB | 20000 | |
| 8-core 32000 MB | 28000 | |
| 16-core 32000 MB | 32000 | |
| 16-core 64000 MB | 40000 | |
| 16-core 96000 MB | 40000 | |
| 16-core 128000 MB | 40000 | 25GB - 6000GB |
| 24-core 192000 MB | 60000 | 25GB - 6000GB |
| 24-core 244000 MB | 60000 | 25GB - 8000GB |
| 32-core 256000 MB | 80000 | |
| 48-core 488000 MB | 120000 | 25GB - 12000GB |
| 80-core 690000 MB | 140000 | |
Dedicated | 2-core 16000 MB | 8000 | 25GB - 4000GB |
| 4-core 16000 MB | 10000 | |
| 4-core 24000 MB | 13000 | |
| 4-core 32000 MB | 16000 | |
| 8-core 32000 MB | 32000 | |
| 8-core 48000 MB | 36000 | |
| 8-core 64000 MB | 40000 | |
| 12-core 48000 MB | 36000 | 25GB - 8000GB |
| 12-core 72000 MB | 40000 | |
| 12-core 96000 MB | 48000 | |
| 16-core 64000 MB | 60000 | |
| 16-core 96000 MB | 60000 | |
| 16-core 128000 MB | 60000 | |
| 24-core 96000 MB | 72000 | |
| 24-core 144000 MB | 76000 | |
| 24-core 192000 MB | 80000 | |
| 32-core 128000 MB | 80000 | |
| 32-core 192000 MB | 90000 | |
| 32-core 256000 MB | 100000 | |
| 48-core 192000 MB | 120000 | 25GB - 10000GB |
| 48-core 288000 MB | 140000 | |
| 48-core 384000 MB | 140000 | |
| 64-core 256000 MB | 150000 | |
| 64-core 384000 MB | 150000 | |
| 64-core 512000 MB | 150000 | 25GB - 12000GB |
| 90-core 720000 MB | 150000 | |
Note:
The storage space cap of an instance specification may vary by region as displayed on the purchase page.
Single-node (SSD cloud disk)
Isolation policy | CPU and Memory | IOPS performance | Throughput performance | Storage capacity |
Basic | 1-core 1000 MB | Random IOPS = min{1800 + 30 × capacity (GB), 26000} Maximum IOPS: 26000 | Throughput = min{120 + 0.2 × capacity (GB), 260} Maximum Throughput (MB/s): 260 MB/s | 20GB - 32000GB |
| | | | 1-core 2000 MB |
| | | | 2-core 4000 MB |
| | | | 2-core 8000 MB |
| | | | 4-core 8000 MB |
| | | | 4-core 16000 MB |
| | | | 8-core 16000 MB |
| | | | 8-core 32000 MB |
Single-node (Enhanced SSD cloud disk)
Isolation policy | CPU and Memory | IOPS performance | Throughput performance | Storage capacity |
Basic | 1-core 1000 MB | Random IOPS = min{1800 + 50 × capacity (GB), 50000} Maximum IOPS: 50000 | Throughput = min{120 + 0.5 × capacity (GB), 350} Maximum Throughput (MB/s): 350 MB/s | 20GB - 32000GB |
| | | | 1-core 2000 MB |
| | | | 2-core 4000 MB |
| | | | 2-core 8000 MB |
| | | | 4-core 8000 MB |
| | | | 4-core 16000 MB |
| | | | 8-core 16000 MB |
| | | | 8-core 32000 MB |
Was this page helpful?
You can also Contact Sales or Submit a Ticket for help.
Yes
No