The article walks through a real‑world MySQL performance case where a 100‑million‑row table caused SLA alerts, analyzes slow‑query logs, demonstrates index redesign, compares online DDL with pt‑osc, and shows how batch deletions by primary key dramatically reduce delete time and replication lag.
This article describes a step‑by‑step procedure for safely dropping a massive MySQL history_str table—including creating a new table, renaming, using hard links, staged drops, and a truncate script—to avoid instance hangs, replication lag, and I/O pressure while freeing disk space.
This guide explains why a single massive DELETE on a 500‑million‑row table creates long‑running transactions and locks, and shows step‑by‑step techniques—date‑range batching, primary‑key range slicing, and insert‑instead‑of‑delete—to break the operation into manageable chunks and improve performance.
This article explains practical strategies for adding a new column to a MySQL table with tens of millions of rows, including creating a temporary table, copying data, renaming tables, and alternative replica‑based or third‑party methods to avoid long locks and potential crashes.
This article analyzes a MySQL master‑slave instance with a massive arrival_record table, identifies slow‑query causes using pt‑query‑digest and tcpdump, proposes index redesign, demonstrates backup/restore with mydumper, compares online DDL and pt‑osc, and presents batch‑delete strategies that dramatically reduce SLA‑triggering latency.
