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 MySQLKernel FeaturesPerformance FeaturesLarge Transaction Binlog Optimization
Large Transaction Binlog Optimization
Last updated: 2024-11-14 10:42:14
Background
When a large transaction is executed in the database, execution of other transactions will slow down. The sign for successfully executing a transaction is its successful commit, but a transaction can be committed only after its binlogs are written to a file. Different transactions should queue up to write their binlogs to the binlog file, that is, only one transaction can write binlogs at a time. If a transaction has a larger binlog size, such as 100 GB, its binlog writing time is longer. In this case, other transactions in the queue are forced to wait for the large transaction to finish writing binlogs, so the execution of other transactions is very slow.
Overview
When a large transaction is committed, a large amount of binlogs are written, causing delays in the commit of other transactions. Through optimization of such scenarios by the Tencent Cloud kernel team, the binlogs generated by a large transaction are redirected to a new temporary file, to prevent other transactions from being blocked by the large transaction and avoid extra processing time. After the large transaction is committed, the temporary file will be updated as the official binlog file and the original data mapping relationship will also be updated.
Supported Versions
Kernel version 3.1.12 or later for TDSQL-C for MySQL 8.0.
Use Cases
In scenarios where a large transaction is executed together with other transactions in the database, this feature is used to shorten delays of other transactions caused by committing a large transaction.
Use Instructions
This feature is used with the txsql_non_blocking_binlog_threshold parameter. Set this parameter to a non-default value to use this feature. Detailed parameter descriptions are as follows:
Name | Global or Not | Type | Default Value | Value Range | Description |
txsql_non_blocking_binlog_threshold | Global | ulong | UINT64_MAX | 134217728-UINT64_MAX | When the binlog size of a transaction is greater than or equal to this value (unit: byte), the transaction will be committed by using the large transaction binlog optimization method. |
Was this page helpful?
You can also Contact Sales or Submit a Ticket for help.
Yes
No