GreatSQL, a MySQL-compatible database, has released version 8.4.4-5 with a notable performance feature: direct binlog flush for large transactions. Traditionally, when a transaction's binlog cache exceeds a threshold, the database must read the cache back and rewrite it into the binlog file, causing extra I/O and latency. The new approach promotes the cache file directly to a binlog file, eliminating the read-back step. This is particularly beneficial for bulk operations, large imports, or any workload with heavy write transactions. Early testing suggests significant reductions in commit time and disk I/O for such scenarios. For teams running MySQL-compatible databases with large transactional workloads, this feature offers a low-risk way to improve throughput without schema changes. It also highlights how community forks like GreatSQL are pushing performance boundaries beyond upstream MySQL.
GreatSQL 8.4.4-5 introduces a feature that writes large-transaction binlog cache files directly to disk as binlog files, avoiding read-back and rewrite overhead. This reduces I/O and improves commit latency for big transactions.