iperf3 + nload: Network Diagnosis
Your gigabit link drops to 200 Mbps and you don't know why. iperf3 measures throughput honestly, nload visualizes traffic — together they find the bottleneck fast.
All the articles with the tag "performance".
Your gigabit link drops to 200 Mbps and you don't know why. iperf3 measures throughput honestly, nload visualizes traffic — together they find the bottleneck fast.
Stop trusting marketing IOPS numbers. fio measures what your disk actually does on your workload — sequential, random, mixed. Here's how to read the output honestly.
CUDA vs ROCm for AI on Linux: NVIDIA's easy path, AMD's emotional journey, and why CPU inference isn't dead yet. Real Docker setups included.
Learn how to set Docker resource limits for memory, CPU, swap, and PIDs. Practical guide with real-world sizing examples, OOM killer behavior, and cgroups explained.
Speed up Ansible playbooks with pipelining, forks, fact caching, and async tasks — stop watching the spinning wheel on every play.
Make Plex actually fast: enable hardware transcoding, fix remote access without relay, tune Docker env vars, and decide if Jellyfin is calling your name.
ulimit and cgroups v2: set per-process CPU, memory, and file limits, use systemd slice controls, and keep one runaway service from killing your server.
Squeeze every MB/s from WireGuard: MTU sizing, GSO/GRO CPU offloading, AllowedIPs routing, PersistentKeepalive tradeoffs, and iperf3 benchmarks included.
Linux ships with conservative kernel defaults. These sysctl settings tune your server for networking, memory, and file I/O — with explanations, not just paste-and-pray values.
WireGuard is fast out of the box, but default config leaves throughput on the table. Tune MTU, use the kernel module, and benchmark what you actually get.
Your Linux box has hundreds of kernel knobs in /proc/sys that nobody ever touches. Most don't matter — here are the handful that actually improve a Docker host.
A kernel upgrade halved one team's PostgreSQL throughput. The fix was kernel tuning: huge pages, THP, swappiness, I/O scheduler. Here's what matters and why.