- Release Notes and Announcements
- Release Notes
- Announcements
- Announcement on Release of New Upgrade Mechanism for Kernel Minor Version
- Announcement on Optimization of Instance Storage Capacity, IOPS, and I/O Bandwidth
- Announcement on Some APIs with CAM Authentication Integrated
- Announcement on Sales Suspension of Some General Specifications
- Announcement on Some APIs Integrated with CAM Authentication
- Announcement on Some APIs with CAM Authentication Integrated
- Announcement on Change of Part of Parameters
- Announcement on Update of Database Audit Feature
- Announcement on Authentication of a Newly Added API Interface of Database Audit
- Announcement on Change of Public Network Linkage
- TDSQL-C for MySQL Audit Service Update
- Announcement on Supplementary Charge for Clusters with Pay-as-You-Go Storage Billing Mode
- Announcement on New APIs Integrated with CAM Permissions
- Announcement on the Release of New Version of Database Proxy
- Emergency Fix for Certain Monitoring Metrics
- Monitoring Metric Optimization
- Change to Database Audit Resource ID
- Ops Change
- Storage Price Adjustment Notification
- Beginner's Guide
- Product Introduction
- Kernel Features
- Kernel Overview
- Kernel Version Release Notes
- Optimized Kernel Version
- Functionality Features
- Performance Features
- Columns Syntax
- Correlated Subquery Result Cache
- Global Index
- Binlog Write Optimization
- Large Transaction Binlog Optimization
- Binlog Purging Performance Optimization
- Optimization of Plan Caching Point Query
- Auto-Increment Column Persistence
- Invisible Index
- Computation Pushdown
- Parallel Initialization of InnoDB Buffer Pool
- Security Features
- Stability Feature
- Purchase Guide
- Getting Started
- Database Audit
- Serverless Service
- Operation Guide
- Switching Cluster Page View in Console
- Database Connection
- Instance Management
- Configuration Adjustment
- Cluster Management
- Scaling Instance
- Database Proxy
- Database Proxy Overview
- Use Limits
- Database Proxy Kernel Features
- Managing Database Proxy
- Enabling Database Proxy
- Setting Database Proxy Address
- Modifying or Deleting Connection Addresses
- Viewing and Changing the Access Policy
- Rebalancing the Load
- Transaction Split Feature
- Access Mode
- Adjusting Database Proxy Configuration
- Switching Database Proxy Network
- Viewing Database Proxy Monitoring Data
- Disabling Database Proxy
- Automatic Read/Write Separation
- Connection Pool Feature
- Other Features
- Account Management
- Database Management
- Database Management Tool
- Columnar Storage Index (CSI)
- Parameter Configuration
- Multi-AZ Deployment
- Backup and Restoration
- Operation Log
- Data Migration
- Parallel Query
- 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
- API Documentation
- History
- Introduction
- API Category
- Making API Requests
- Billing APIs
- Instance APIs
- CloseClusterPasswordComplexity
- CopyClusterPasswordComplexity
- DescribeClusterDetail
- DescribeClusterPasswordComplexity
- ModifyClusterPasswordComplexity
- OpenClusterPasswordComplexity
- UpgradeClusterVersion
- UpgradeInstance
- SetRenewFlag
- OfflineCluster
- ModifyMaintainPeriodConfig
- IsolateInstance
- IsolateCluster
- DescribeMaintainPeriod
- DescribeInstanceSpecs
- DescribeClusters
- CreateClusters
- AddInstances
- OfflineInstance
- DescribeInstanceDetail
- DescribeClusterInstanceGrps
- DescribeInstances
- ActivateInstance
- ModifyInstanceName
- ModifyClusterName
- SearchClusterTables
- SearchClusterDatabases
- RestartInstance
- Multi-AZ APIs
- Account APIs
- Audit APIs
- Database Proxy APIs
- Backup and Restoration APIs
- Parameter Management APIs
- Performance Analysis APIs
- Serverless APIs
- ResourcePackage APIs
- Other APIs
- CloseWan
- CreateClusterDatabase
- DeleteClusterDatabase
- DescribeClusterDetailDatabases
- ModifyClusterDatabase
- OpenWan
- SwitchClusterVpc
- OpenReadOnlyInstanceExclusiveAccess
- OpenClusterReadOnlyInstanceGroupAccess
- ModifyDBInstanceSecurityGroups
- DescribeProjectSecurityGroups
- DescribeDBSecurityGroups
- SwitchProxyVpc
- DescribeFlow
- DescribeZones
- ModifyVipVport
- Data Types
- Error Codes
- FAQs
- Service Agreement
- TDSQL-C Policy
- General References
- Glossary
- Contact Us
- Release Notes and Announcements
- Release Notes
- Announcements
- Announcement on Release of New Upgrade Mechanism for Kernel Minor Version
- Announcement on Optimization of Instance Storage Capacity, IOPS, and I/O Bandwidth
- Announcement on Some APIs with CAM Authentication Integrated
- Announcement on Sales Suspension of Some General Specifications
- Announcement on Some APIs Integrated with CAM Authentication
- Announcement on Some APIs with CAM Authentication Integrated
- Announcement on Change of Part of Parameters
- Announcement on Update of Database Audit Feature
- Announcement on Authentication of a Newly Added API Interface of Database Audit
- Announcement on Change of Public Network Linkage
- TDSQL-C for MySQL Audit Service Update
- Announcement on Supplementary Charge for Clusters with Pay-as-You-Go Storage Billing Mode
- Announcement on New APIs Integrated with CAM Permissions
- Announcement on the Release of New Version of Database Proxy
- Emergency Fix for Certain Monitoring Metrics
- Monitoring Metric Optimization
- Change to Database Audit Resource ID
- Ops Change
- Storage Price Adjustment Notification
- Beginner's Guide
- Product Introduction
- Kernel Features
- Kernel Overview
- Kernel Version Release Notes
- Optimized Kernel Version
- Functionality Features
- Performance Features
- Columns Syntax
- Correlated Subquery Result Cache
- Global Index
- Binlog Write Optimization
- Large Transaction Binlog Optimization
- Binlog Purging Performance Optimization
- Optimization of Plan Caching Point Query
- Auto-Increment Column Persistence
- Invisible Index
- Computation Pushdown
- Parallel Initialization of InnoDB Buffer Pool
- Security Features
- Stability Feature
- Purchase Guide
- Getting Started
- Database Audit
- Serverless Service
- Operation Guide
- Switching Cluster Page View in Console
- Database Connection
- Instance Management
- Configuration Adjustment
- Cluster Management
- Scaling Instance
- Database Proxy
- Database Proxy Overview
- Use Limits
- Database Proxy Kernel Features
- Managing Database Proxy
- Enabling Database Proxy
- Setting Database Proxy Address
- Modifying or Deleting Connection Addresses
- Viewing and Changing the Access Policy
- Rebalancing the Load
- Transaction Split Feature
- Access Mode
- Adjusting Database Proxy Configuration
- Switching Database Proxy Network
- Viewing Database Proxy Monitoring Data
- Disabling Database Proxy
- Automatic Read/Write Separation
- Connection Pool Feature
- Other Features
- Account Management
- Database Management
- Database Management Tool
- Columnar Storage Index (CSI)
- Parameter Configuration
- Multi-AZ Deployment
- Backup and Restoration
- Operation Log
- Data Migration
- Parallel Query
- 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
- API Documentation
- History
- Introduction
- API Category
- Making API Requests
- Billing APIs
- Instance APIs
- CloseClusterPasswordComplexity
- CopyClusterPasswordComplexity
- DescribeClusterDetail
- DescribeClusterPasswordComplexity
- ModifyClusterPasswordComplexity
- OpenClusterPasswordComplexity
- UpgradeClusterVersion
- UpgradeInstance
- SetRenewFlag
- OfflineCluster
- ModifyMaintainPeriodConfig
- IsolateInstance
- IsolateCluster
- DescribeMaintainPeriod
- DescribeInstanceSpecs
- DescribeClusters
- CreateClusters
- AddInstances
- OfflineInstance
- DescribeInstanceDetail
- DescribeClusterInstanceGrps
- DescribeInstances
- ActivateInstance
- ModifyInstanceName
- ModifyClusterName
- SearchClusterTables
- SearchClusterDatabases
- RestartInstance
- Multi-AZ APIs
- Account APIs
- Audit APIs
- Database Proxy APIs
- Backup and Restoration APIs
- Parameter Management APIs
- Performance Analysis APIs
- Serverless APIs
- ResourcePackage APIs
- Other APIs
- CloseWan
- CreateClusterDatabase
- DeleteClusterDatabase
- DescribeClusterDetailDatabases
- ModifyClusterDatabase
- OpenWan
- SwitchClusterVpc
- OpenReadOnlyInstanceExclusiveAccess
- OpenClusterReadOnlyInstanceGroupAccess
- ModifyDBInstanceSecurityGroups
- DescribeProjectSecurityGroups
- DescribeDBSecurityGroups
- SwitchProxyVpc
- DescribeFlow
- DescribeZones
- ModifyVipVport
- Data Types
- Error Codes
- FAQs
- Service Agreement
- TDSQL-C Policy
- General References
- Glossary
- Contact Us
This document lists the performance comparison test results between TDSQL-C for MySQL and TencentDB for MySQL in the full cache scenario.
Full Cache Scenario Overview
In the full cache scenario, as all data can be put into the cache, the disk doesn't need to be read and written to update the cache during queries.
Full Cache Scenario Test Conclusion
The higher the instance specification, the more obvious the performance advantage of TDSQL-C for MySQL. TencentDB for MySQL's write and read-write performance reaches a bottleneck at the 32-core specification, but TDSQL-C for MySQL can further increase the QPS with more CPU cores.
In most scenarios, TDSQL-C for MySQL can achieve a CPU utilization of above 90% on compute nodes. The test shows that the resource utilization of TDSQL-C for MySQL is better than that of TencentDB for MySQL.
TDSQL-C for MySQL is more stable in terms of request delay (RTT) and almost doesn't jitter at all when the dataset is fully cached.
Dataset Characteristics | Test Scenario | Read Type | Conclusion |
Full cache | Write | - | TDSQL-C for MySQL has a higher performance |
| Read | POINT SELECT | TDSQL-C for MySQL has a higher performance |
| Read | RANGE SELECT | TDSQL-C for MySQL and TencentDB for MySQL have generally the same performance under low specifications, but the latter outperforms the former under high specifications |
| Read-write | POINT SELECT | TDSQL-C for MySQL has a higher performance |
| Read-write | RANGE SELECT | TDSQL-C for MySQL and TencentDB for MySQL have generally the same performance under most specifications |
Full Cache Scenario Test Results
Scenario 1: Write
Specification | Concurrency | Table Size | Tables | QPS | |
| | | | TencentDB for MySQL | TDSQL-C for MySQL |
2-core 16 GB MEM | 96 | 25000 | 250 | 15665 | 30054 |
4-core 16 GB MEM | 192 | 25000 | 250 | 40574 | 53334 |
4-core 32 GB MEM | 192 | 25000 | 250 | 42966 | 53713 |
8-core 32 GB MEM | 256 | 25000 | 250 | 67229 | 100737 |
8-core 64 GB MEM | 256 | 25000 | 250 | 76955 | 99480 |
16-core 64 GB MEM | 512 | 25000 | 250 | 134590 | 181035 |
16-core 96 GB MEM | 512 | 25000 | 250 | 142419 | 181029 |
16-core 128 GB MEM | 512 | 25000 | 250 | 144529 | 181482 |
32-core 128 GB MEM | 1000 | 25000 | 250 | 224786 | 319913 |
32-core 256 GB MEM | 1000 | 25000 | 250 | 220350 | 370294 |
64-core 256 GB MEM | 1000 | 25000 | 250 | 236079 | 448221 |
Scenario 2: Read (POINT SELECT)
Specification | Concurrency | Table Size | Tables | QPS | |
| | | | TencentDB for MySQL | TDSQL-C for MySQL |
2-core 16 GB MEM | 1500 | 25000 | 250 | 38633 | 57153 |
4-core 16 GB MEM | 1500 | 25000 | 250 | 80398 | 108368 |
4-core 32 GB MEM | 1500 | 25000 | 250 | 81100 | 108639 |
8-core 32 GB MEM | 1500 | 25000 | 250 | 159885 | 185710 |
8-core 64 GB MEM | 1500 | 25000 | 250 | 172800 | 206007 |
16-core 64 GB MEM | 2000 | 25000 | 250 | 313223 | 402101 |
16-core 96 GB MEM | 2000 | 25000 | 250 | 321229 | 402101 |
16-core 128 GB MEM | 2000 | 25000 | 250 | 321617 | 403809 |
32-core 128 GB MEM | 2000 | 25000 | 250 | 409118 | 715886 |
32-core 256 GB MEM | 2000 | 25000 | 250 | 549297 | 719295 |
64-core 256 GB MEM | 2000 | 25000 | 250 | 670026 | 1125180 |
Scenario 3: Read (RANGE SELECT)
Specification | Concurrency | Table Size | Tables | QPS | |
| | | | TencentDB for MySQL | TDSQL-C for MySQL |
2-core 16 GB MEM | 64 | 25000 | 250 | 14474 | 15837 |
4-core 16 GB MEM | 64 | 25000 | 250 | 31523 | 31169 |
4-core 32 GB MEM | 64 | 25000 | 250 | 31988 | 31048 |
8-core 32 GB MEM | 64 | 25000 | 250 | 50362 | 59531 |
8-core 64 GB MEM | 64 | 25000 | 250 | 63686 | 59008 |
16-core 64 GB MEM | 128 | 25000 | 250 | 113098 | 113779 |
16-core 96 GB MEM | 128 | 25000 | 250 | 124928 | 113377 |
16-core 128 GB MEM | 128 | 25000 | 250 | 128728 | 113606 |
32-core 128 GB MEM | 256 | 25000 | 250 | 212540 | 197144 |
32-core 256 GB MEM | 256 | 25000 | 250 | 199970 | 197796 |
64-core 256 GB MEM | 256 | 25000 | 250 | 304502 | 289460 |
Scenario 4: Read-write (POINT SELECT)
Specification | Concurrency | Table Size | Tables | QPS | |
| | | | TencentDB for MySQL | TDSQL-C for MySQL |
2-core 16 GB MEM | 512 | 25000 | 250 | 22554 | 38001 |
4-core 16 GB MEM | 512 | 25000 | 250 | 57841 | 71560 |
4-core 32 GB MEM | 512 | 25000 | 250 | 60797 | 72625 |
8-core 32 GB MEM | 512 | 25000 | 250 | 97243 | 138499 |
8-core 64 GB MEM | 512 | 25000 | 250 | 112912 | 138784 |
16-core 64 GB MEM | 512 | 25000 | 250 | 198182 | 247586 |
16-core 96 GB MEM | 512 | 25000 | 250 | 203479 | 247631 |
16-core 128 GB MEM | 512 | 25000 | 250 | 209947 | 248301 |
32-core 128 GB MEM | 512 | 25000 | 250 | 348721 | 400126 |
32-core 256 GB MEM | 512 | 25000 | 250 | 333932 | 379531 |
64-core 256 GB MEM | 512 | 25000 | 250 | 439984 | 553040 |
Scenario 5: Read-write (RANGE SELECT)
Specification | Concurrency | Table Size | Tables | QPS | |
| | | | TencentDB for MySQL | TDSQL-C for MySQL |
2-core 16 GB MEM | 64 | 25000 | 250 | 13568 | 16072 |
4-core 16 GB MEM | 256 | 25000 | 250 | 33318 | 34553 |
4-core 32 GB MEM | 256 | 25000 | 250 | 33766 | 34321 |
8-core 32 GB MEM | 256 | 25000 | 250 | 55588 | 65190 |
8-core 64 GB MEM | 256 | 25000 | 250 | 62616 | 65701 |
16-core 64 GB MEM | 256 | 25000 | 250 | 111148 | 123984 |
16-core 96 GB MEM | 256 | 25000 | 250 | 131182 | 124659 |
16-core 128 GB MEM | 384 | 25000 | 250 | 130767 | 125947 |
32-core 128 GB MEM | 384 | 25000 | 250 | 218580 | 214861 |
32-core 256 GB MEM | 384 | 25000 | 250 | 210922 | 216303 |
64-core 256 GB MEM | 384 | 25000 | 250 | 308399 | 312941 |
Yes
No
Was this page helpful?