This article explains how MySQL 8.0.32 processes the flush, sync, and commit subphases during a two‑phase commit, detailing the roles of leader and follower threads, log handling, system variables, and the conditions that trigger binlog rotation and persistence.
The article explains how executing FLUSH commands on MySQL replicas that are in read_only mode can still write to the binary log, generate new GTIDs, and lead to GTID mismatches between primary and replica, especially when tools like ClickHouse issue such statements.
This article explains the differences between buffers and caches, explores MySQL’s buffer pool architecture, details write‑through/write‑back strategies, and reviews key InnoDB parameters such as innodb_flush_log_at_trx_commit and innodb_flush_method for optimizing data durability and performance.
This article explains the fundamental differences between buffers and caches, details MySQL’s multi‑layer buffer architecture, and examines how write‑through, write‑back, and Direct I/O affect data durability and performance through various InnoDB flush parameters.
This article provides a detailed walkthrough of Netty's internal write and flush processes, explaining how ChannelHandlerContext propagates outbound events, how ChannelOutboundBuffer manages pending data with high/low watermarks, the role of write loops, OP_WRITE handling, and the combined writeAndFlush operation in Java's high‑performance network framework.
The PHP function fastcgi_finish_request flushes all pending response data to the client and terminates the request, allowing the server to continue executing time‑consuming tasks after the client connection has closed, and returns TRUE on success or FALSE on failure.
This article explains the full syntax of Python's print() function, describes each parameter (value, sep, end, file, flush), and provides step‑by‑step examples showing how to output single or multiple values, control separators, line endings, redirect output to files, and force flushing.
This article explains the core mechanisms of HBase—Flush and Compaction—detailing why they are needed, the conditions that trigger Flush, the types and triggers of Compaction, and provides practical recommendations for tuning the most important configuration parameters to improve write and read performance.
The article explains how Elasticsearch’s use of Lucene’s flush mechanism, concurrent shard writes, and IndexWriter buffering lead to an excess of small segments, outlines the flush conditions, and offers guidance on managing write concurrency for better performance.
