RDS for MySQL
RDS for MySQL
RDS for MySQL
Document
What's new
Announcement
Product introduction
Product billing
Billing method
Kernel functions
Feature
Stability
Performance
Quick start
User guide
Managing instances
Changing an instance configuration
Upgrading kernel versions
Managing tags
Managing disaster instances
Managing blue-green deployment
Migrating data
Managing connections
Database proxy
Connecting to an instance
Managing connection endpoints
Diagnosing connections
Managing connection pool modes
Managing access addresses and ports
Managing databases
Account and access authorization
Backup recovery
Backup data
Data recovery
Service availability
Managing logs
Managing data security
Managing allowlists
Configuring SSL encryption
Managing parameters
Monitoring and alerts
Task center
Operation and maintenance events
Backups of deleted instances
Managing cross-regional backups
API reference
V2（2022-01-01）
Global management
Managing instances
Managing connections
Managing accounts
Managing databases
Security encryption
Backup and recovery
Managing parameters
Managing tasks
Event management
Managing logs
Resource plan management
Appendix
SDK reference
Developer tools
Best practice
Performance document
Troubleshooting
- Documentation
RDS for MySQLKernel functionsPerformanceConcurrent binlog flush
Copy page
Download PDFPerformance
Concurrent binlog flush
Copy pageDownload PDFConcurrent binlog flush
This topic describes the binlog concurrent flush optimization feature provided by RDS for MySQL.
Supported version
- MySQL 8.0 version, and the kernel version is MySQL 8.0.43_20251215 and above.
- MySQL 8.4 version, and the kernel version is MySQL 8.4.7_20260415 and above.
tip
You can view the kernel minor version of an instance by Viewing instance information. If the kernel minor version of your instance is not within the supported kernel minor version range, you can Manually upgrading the instance kernel minor version.
Background
When a transaction is committed in MySQL, binlog events are written from the temporary cache of the current session to the binlog file. Since this operation is performed serially, writing to the binlog file often becomes a performance bottleneck for the entire instance.
Feature description
RDS for MySQL optimizes the process of writing transaction binlog events from the temporary cache of the current session to the binlog file. This allows binlog events to be written concurrently, which significantly improves instance performance.
Instructions
Parameter description
The following parameters can be modified to configure the concurrent binlog flush optimization.
Parameter name | Default value | Whether an instance restart is required for the change to take effect | Value range | Scope | Description |
loose_binlog_parallel_flush | OFF | Yes | [ON|OFF] | Global | Enables or disables the binlog concurrent flush optimization feature. Values:
|
Precautions
To use the binlog concurrent flush optimization feature, the instance parameter configuration must meet the following conditions:
- The running value of the sync_binlog parameter is not 1.
- The running value of the innodb_flush_log_at_trx_commit parameter is not 1.
- The running value of the binlog_order_commits parameter is OFF.
Performance data
In tests using the Sysbench oltp_update_non_index script, enabling the binlog concurrent flush optimization feature reduces transaction commit latency and stabilizes QPS, typically improving performance by 10% to 20% in high-concurrency scenarios.
Last updated: 2026.05.28 15:17:55
All rights reserved © Beijing Volcano Engine Technology Co., Ltd2024
