- 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
- Analysis Engine Features
- 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)
- Read-Only Analysis Engine
- 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
- Analysis Engine Features
- 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)
- Read-Only Analysis Engine
- 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 1 TB single table scenario.
Overview
In the 1 TB single table scenario, the test dataset contains 4 billion data records in one single table with a storage space of 1 TB.
Test Conclusion
In the read scenario, 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.
In the write scenario, TDSQL-C for MySQL outperforms TencentDB for MySQL under lower specifications, and as the specifications and data volume increase, its performance advantage gets much greater.
Dataset Characteristics | Test Scenario | Read Type | Conclusion |
1 TB single table | Write | - | TDSQL-C for MySQL has a higher performance |
| Read | POINT SELECT | TDSQL-C for MySQL and TencentDB for MySQL have generally the same performance under most specifications, but the former outperforms the latter under the maximum specification |
| Read | RANGE SELECT | TDSQL-C for MySQL and TencentDB for MySQL have generally the same performance under most 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 |
Test Results
Scenario 1: Write
Specification | Concurrency | Table Size | Tables | QPS | |
| | | | TencentDB for MySQL | TDSQL-C for MySQL |
2-core 16 GB MEM | 256 | 4000000000 | 1 | 10881 | 17816 |
4-core 16 GB MEM | 512 | 4000000000 | 1 | 26827 | 33700 |
4-core 32 GB MEM | 512 | 4000000000 | 1 | 31404 | 41098 |
8-core 32 GB MEM | 512 | 4000000000 | 1 | 44167 | 76047 |
8-core 64 GB MEM | 512 | 4000000000 | 1 | 55609 | 81191 |
16-core 64 GB MEM | 512 | 4000000000 | 1 | 88401 | 134317 |
16-core 96 GB MEM | 512 | 4000000000 | 1 | 97068 | 134923 |
16-core 128 GB MEM | 512 | 4000000000 | 1 | 101274 | 134340 |
32-core 128 GB MEM | 512 | 4000000000 | 1 | 111626 | 196333 |
32-core 256 GB MEM | 512 | 4000000000 | 1 | 131058 | 206395 |
64-core 256 GB MEM | 512 | 4000000000 | 1 | 140587 | 256415 |
Scenario 2: Read
Specification | Concurrency | Table Size | Tables | QPS | |
| | | | TencentDB for MySQL | TDSQL-C for MySQL |
2-core 16 GB MEM | 256 | 4000000000 | 1 | 29135 | 31504 |
4-core 16 GB MEM | 512 | 4000000000 | 1 | 59667 | 61128 |
4-core 32 GB MEM | 512 | 4000000000 | 1 | 66219 | 64707 |
8-core 32 GB MEM | 512 | 4000000000 | 1 | 119374 | 128884 |
8-core 64 GB MEM | 512 | 4000000000 | 1 | 127005 | 129857 |
16-core 64 GB MEM | 1000 | 4000000000 | 1 | 229007 | 210873 |
16-core 96 GB MEM | 1000 | 4000000000 | 1 | 230460 | 217415 |
16-core 128 GB MEM | 1000 | 4000000000 | 1 | 236767 | 228319 |
32-core 128 GB MEM | 1000 | 4000000000 | 1 | 377009 | 368868 |
32-core 256 GB MEM | 1000 | 4000000000 | 1 | 412356 | 421931 |
64-core 256 GB MEM | 1000 | 4000000000 | 1 | 569523 | 794997 |
Scenario 3: Read
Specification | Concurrency | Table Size | Tables | QPS | |
| | | | TencentDB for MySQL | TDSQL-C for MySQL |
2-core 16 GB MEM | 32 | 4000000000 | 1 | 11773 | 14358 |
4-core 16 GB MEM | 64 | 4000000000 | 1 | 25688 | 26093 |
4-core 32 GB MEM | 64 | 4000000000 | 1 | 26826 | 28748 |
8-core 32 GB MEM | 128 | 4000000000 | 1 | 48998 | 54387 |
8-core 64 GB MEM | 128 | 4000000000 | 1 | 54987 | 60345 |
16-core 64 GB MEM | 256 | 4000000000 | 1 | 103212 | 113117 |
16-core 96 GB MEM | 256 | 4000000000 | 1 | 105302 | 113609 |
16-core 128 GB MEM | 256 | 4000000000 | 1 | 108209 | 114218 |
32-core 128 GB MEM | 512 | 4000000000 | 1 | 187161 | 190716 |
32-core 256 GB MEM | 512 | 4000000000 | 1 | 192407 | 190472 |
64-core 256 GB MEM | 1000 | 4000000000 | 1 | 308631 | 319047 |
Scenario 4: Read-write
Specification | Concurrency | Table Size | Tables | QPS | |
| | | | TencentDB for MySQL | TDSQL-C for MySQL |
2-core 16 GB MEM | 64 | 4000000000 | 1 | 16313 | 24150 |
4-core 16 GB MEM | 64 | 4000000000 | 1 | 38896 | 42051 |
4-core 32 GB MEM | 128 | 4000000000 | 1 | 47036 | 53506 |
8-core 32 GB MEM | 256 | 4000000000 | 1 | 80167 | 103935 |
8-core 64 GB MEM | 256 | 4000000000 | 1 | 93335 | 123395 |
16-core 64 GB MEM | 512 | 4000000000 | 1 | 135267 | 220769 |
16-core 96 GB MEM | 512 | 4000000000 | 1 | 140926 | 229214 |
16-core 128 GB MEM | 512 | 4000000000 | 1 | 152629 | 234357 |
32-core 128 GB MEM | 512 | 4000000000 | 1 | 199042 | 381067 |
32-core 256 GB MEM | 512 | 4000000000 | 1 | 223027 | 384323 |
64-core 256 GB MEM | 1000 | 4000000000 | 1 | 283722 | 520265 |
Scenario 5: Read-write (RANGE SELECT)
Specification | Concurrency | Table Size | Tables | QPS | |
| | | | TencentDB for MySQL | TDSQL-C for MySQL |
2-core 16 GB MEM | 256 | 4000000000 | 1 | 10177 | 12129 |
4-core 16 GB MEM | 512 | 4000000000 | 1 | 23475 | 22560 |
4-core 32 GB MEM | 512 | 4000000000 | 1 | 27023 | 26009 |
8-core 32 GB MEM | 512 | 4000000000 | 1 | 48087 | 52183 |
8-core 64 GB MEM | 512 | 4000000000 | 1 | 53915 | 53766 |
16-core 64 GB MEM | 512 | 4000000000 | 1 | 98038 | 95518 |
16-core 96 GB MEM | 512 | 4000000000 | 1 | 97504 | 97117 |
16-core 128 GB MEM | 512 | 4000000000 | 1 | 101461 | 99140 |
32-core 128 GB MEM | 512 | 4000000000 | 1 | 154222 | 171150 |
32-core 256 GB MEM | 512 | 4000000000 | 1 | 182955 | 183249 |
64-core 256 GB MEM | 512 | 4000000000 | 1 | 246526 | 266539 |
Yes
No
Was this page helpful?