0 views collected around this technical thread.
This article explains Linux disk I/O performance metrics, benchmark methods, observation tools like iostat, pidstat, and iotop, and walks through a practical case of diagnosing and resolving an I/O spike caused by the jbd2 journaling process.
This article analyzes a real‑world migration from MongoDB to the open‑source Pika KV store, demonstrating how adjusting the max‑write‑buffer‑size parameter dramatically improves disk I/O characteristics and raises query‑per‑second throughput from 3 K to 40 K.
This article walks through generating a heavy‑load MySQL workload, using top, iostat, and iotop to pinpoint high disk I/O, mapping OS thread IDs back to MySQL sessions, and safely killing the offending query to relieve pressure.
This guide explains how to monitor Linux server performance using built‑in tools such as top, vmstat, pidstat, iostat, netstat, sar and tcpdump, interpreting their output to diagnose CPU, memory, disk I/O and network issues quickly and effectively.
This article explains the meaning of iostat fields, the limitations of svctm and await, how /proc/diskstats provides raw counters, and offers formulas and examples for accurately analyzing Linux disk performance.
This guide walks you through essential Linux server monitoring tools—top, vmstat, pidstat, iostat, netstat, sar, and tcpdump—explaining each metric, how to interpret CPU, memory, disk, and network statistics, and offering practical tips for troubleshooting performance bottlenecks.
This article introduces key Linux monitoring utilities—top, vmstat, pidstat, iostat, netstat, sar, and tcpdump—explains the meaning of their output fields, and shows how to use them to diagnose CPU, memory, disk, and network performance issues on production servers.