tencent cloud

TDSQL-C for MySQL

Release Notes and Announcements
Release Notes
Product Announcements
Beginner's Guide
Product Introduction
Overview
Strengths
Use Cases
Architecture
Product Specifications
Instance Types
Product Feature List
Database Versions
Regions and AZs
Common Concepts
Use Limits
Suggestions on Usage Specifications
Kernel Features
Kernel Overview
Kernel Version Release Notes
Optimized Kernel Version
Functionality Features
Performance Features
Security Features
Stability Feature
Analysis Engine Features
Inspection and Repair of Kernel Issues
Purchase Guide
Billing Overview
Product Pricing
Creating Cluster
Specification Adjustment Description
Renewal
Payment Overdue
Refund
Change from Pay-as-You-Go to Yearly/Monthly Subscription
Change from Pay-as-You-Go to Serverless Billing
Value-Added Services Billing Overview
Viewing Billing Statements
Getting Started
Database Audit
Overview
Viewing Audit Instance List
Enabling Audit Service
Viewing Audit Logs
Log Shipping
Post-Event Alarm Configuration
Modifying Audit Rule
Modifying Audit Service
Disabling Audit Service
Audit Rule Template
Viewing Audit Task
Authorizing Sub-User to Use Database Audit
Serverless Service
Serverless Introduction
Creating and Managing a Serverless Cluster
Elastic Scaling Management Tool
Serverless Resource Pack
Multi-AZ Deployment
Configuration Change
FAQs
Serverless Cost Estimator
Operation Guide
Operation Overview
Switching Cluster Page View in Console
Database Connection
Instance Management
Configuration Adjustment
Instance Mode Management
Cluster Management
Scaling Instance
Database Proxy
Account Management
Database Management
Database Management Tool
Parameter Configuration
Multi-AZ Deployment
GD
Backup and Restoration
Operation Log
Data Migration
Parallel Query
Columnar Storage Index (CSI)
Analysis Engine
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
Security White Paper
Performance White Paper
Troubleshooting
Connection Issues
Performance Issues
API Documentation
History
Introduction
API Category
Making API Requests
Instance APIs
Multi-Availability Zone APIs
Other APIs
Audit APIs
Database Proxy APIs
Backup and Recovery APIs
Parameter Management APIs
Billing APIs
serverless APIs
Resource Package APIs
Account APIs
Performance Analysis APIs
Data Types
Error Codes
FAQs
Basic Concepts
Purchase and Billing
Compatibility and Format
Connection and Network
Features
Console Operations
Database and Table
Performance and Log
Database Audit
Between TDSQL-C for MySQL and TencentDB for MySQL
Service Agreement
Service Level Agreement
Terms of Service
TDSQL-C Policy
Privacy Policy
Data Privacy and Security Agreement
General References
Standards and Certifications
Glossary
Contact Us

Test Environments

PDF
포커스 모드
폰트 크기
마지막 업데이트 시간: 2025-12-25 09:45:59
This document introduces the performance test environment for TDSQL-C for MySQL.

Test Regions

Chongqing.
Note:
The test Cloud Virtual Machine (CVM) and TDSQL-C for MySQL instances must be in the same Virtual Private Cloud (VPC) network and deployed in the same availability zone (AZ) in the same region, to ensure the validity of the performance test.

Client Information Used for the Test

Category
Description
Client type
CVM.
Client specifications
S5.4XLARGE32 (Standard S5; 16 cores and 32 GB).
Client operating system (OS)
CentOS 7.
Number of clients
1 (1 client needs to be added when the number of concurrent threads exceeds 1000, and so on).

Test Instance Information

Category
Description
Instance mode
TDSQL-C for MySQL provisioned resource cluster.
Compute instance configuration
A cluster with only 1 read-write instance is used for read-only, mixed read-write, and write-only performance tests.
AZ deployment
Single AZ.
Database version
MySQL 8.0.
Parameters
1. The default parameter template is created and used. Set the cluster type to general and the database version to TDSQL-C for MySQL 8.0.
2. After the default parameter template is created, the following parameters are adjusted.
2.1 Set log_bin to off.
2.2 Set thread_handling to pool-of-threads.
2.3 Set innodb_log_sync_method to async.
Note:
The parameters log_bin and innodb_log_sync_method cannot be directly modified currently. If you need to modify them, submit a ticket for modification.
For operations about how to create a parameter template, see Using Parameter Templates.
For operations about how to set instance parameters, see Setting Instance Parameters.
VPC network latency
0.6 ms.

Test Instance Type/Specifications

In the case of full cache and large data sets, the test instance type and specifications are shown in the table below.
Instance Type
Instance Specifications
Exclusive
2 cores and 4 GB
4 cores and 8 GB
8 cores and 16 GB
8 cores and 32 GB
8 cores and 64 GB
16 cores and 64 GB
16 cores and 96 GB
16 cores and 128 GB
24 cores and 144 GB
32 cores and 128 GB
32 cores and 256 GB
64 cores and 256 GB
64 cores and 512 GB
88 cores and 710 GB

도움말 및 지원

문제 해결에 도움이 되었나요?

피드백