Learn how to maximize Nginx throughput by correctly configuring worker_processes, worker_connections, enabling epoll, and using accept_mutex, with practical examples, formulae, and system‑level tweaks to avoid common pitfalls like CPU oversubscription and 'too many open files' errors.
This article explains the thundering herd problem in Nginx when many workers compete for new connections and provides four practical solutions—accept_mutex, reuseport, multi_accept, and keepalive_timeout—along with configuration examples to improve high‑concurrency performance.
This article explains the thundering herd issue in Nginx’s multi‑process model, detailing both accept‑ and epoll‑related herd problems, their causes, and practical mitigation techniques such as kernel‑level improvements, Nginx’s accept_mutex, dynamic load balancing, and the SO_REUSEPORT feature.
This article explains the thundering herd phenomenon in multi‑process servers, describes Nginx's master‑worker architecture and its use of epoll, and evaluates three mitigation techniques—accept_mutex, EPOLLEXCLUSIVE, and SO_REUSEPORT—along with relevant source code examples.
This article explains the thundering herd phenomenon in multi‑process servers, walks through Nginx’s master‑worker architecture and its use of epoll, and compares three practical mitigation techniques—accept_mutex, EPOLLEXCLUSIVE, and SO_REUSEPORT—complete with code excerpts and configuration examples.
This article explains the thundering herd phenomenon in multi‑process servers, examines Nginx’s master‑worker architecture, and details three mitigation techniques—accept_mutex, EPOLLEXCLUSIVE, and SO_REUSEPORT—showing how each leverages epoll and kernel features to reduce unnecessary wake‑ups.
This article explains the thundering herd effect in multi‑process servers, describes Nginx's master‑worker architecture and its use of epoll, then compares three mitigation techniques—accept_mutex, EPOLLEXCLUSIVE, and SO_REUSEPORT—showing code snippets and performance insights.
This article walks through Linux process states, fork/exec creation, CPU vs load metrics, network I/O models, and a real‑world Nginx high‑load case, showing how strace, accept_mutex, and SO_REUSEPORT can resolve the issue.
NGINX 1.9.1 introduces the SO_REUSEPORT socket option, allowing multiple workers to share the same IP and port, reducing lock contention and improving throughput, with detailed configuration steps and benchmark data demonstrating up to three‑fold request rate gains.
The article walks through a real‑world investigation of an Nginx HTTP forward proxy on an Alibaba Cloud server that stops accepting new connections after a while, detailing hypothesis testing, strace analysis, fastsocket feature toggles, accept_mutex behavior, and the final fix by adjusting the NIC's RPS settings.
