1 views collected around this technical thread.
This article explains MySQL 8.0.32 InnoDB's two‑phase commit process, detailing the flush, sync, and commit sub‑stages, the concept of group commit, and how queues and mutexes coordinate transaction logging to reduce redundant disk writes.
This article explains why master‑slave lag occurs in MySQL, describes the evolution of parallel replication schemes—including group‑commit, Commit‑Parent‑Based, Lock‑Based, and WRITESET approaches—shows benchmark results, and provides practical configuration steps to enable high‑performance parallel replication.
Through a series of experiments using MySQL 8.0, this article demonstrates how group commit reduces I/O operations by consolidating multiple transactions into a single commit group, showing that doubling load increases runtime modestly while transaction count and commit groups rise significantly, highlighting performance benefits.
MySQL achieves crash‑safe durability by employing a write‑ahead log architecture that records changes in redo, undo, and binary logs, coordinates them through two‑phase and group commit to maintain order, and uses a structured recovery process to replay or roll back transactions after any failure.
This article explains how MySQL's enhanced multi‑threaded slave (MTS) feature, introduced in 5.6.3 and refined in 5.7, reduces replication lag, describes the DTLE component that enables MTS parallel replay, shows the required configuration parameters, and presents performance test results demonstrating up to six‑fold speed improvement.
This article explains MySQL's binlog group commit mechanism, detailing the three stages—Flush, Sync, and Commit—how they interact with redo logs and crash‑safe parameters, and analyzes a known bug in the Sync stage that was fixed in later MySQL versions.
This article examines MySQL bug #89370, detailing how configuring semi‑synchronous replication with multiple slaves can cause a slave to stop receiving data for minutes despite normal replication status, and explains the underlying mechanisms, reproduction steps, and root cause of the issue.
This article explains the ACID properties, write‑ahead logging, and how RocksDB implements a three‑step write path and a leader‑follower Group Commit mechanism to improve transaction throughput by batching fsync operations.
This article presents a series of MySQL backend improvements—including Group Commit redesign, DDL fast‑fail handling, GTID allocation refinements, persistent InnoDB auto‑increment values, replication parallelism, and key‑partition hash algorithm changes—detailing motivations, implementation steps, and performance results.
This article explains MySQL's Group Commit mechanism, DDL fast‑fail enhancements, GTID allocation optimizations, fixes for InnoDB auto‑increment duplication after restart, and the evolution of replication performance from 5.5 to 5.7, including detailed code snippets and benchmark results.
This article presents a comprehensive technical overview of MySQL performance tuning and feature enhancements—including group‑commit redesign, DDL fast‑fail, GTID handling, persistent auto‑increment, replication parallelism, and key‑partition hash changes—backed by real‑world test data from Taobao's large‑scale deployment.