Mastering the C10K Challenge: How Nginx Handles 10,000 Concurrent Connections

What is the C10K problem?

C10K stands for "Concurrent 10,000 connections problem", describing the challenge of a single server handling ten thousand simultaneous connections.

Historical background

The term was introduced by Dan Kegel in 1999 when hardware and operating‑system/network‑stack limitations made this a critical issue.

How to solve the C10K problem

The solution can be summarized in four key techniques:

1. I/O multiplexing

Allows a process to monitor multiple file descriptors and receive notifications when any become ready. Key mechanisms include epoll on Linux and kqueue on BSD/macOS. This reduces the need for a thread per connection.

2. Asynchronous non‑blocking I/O

Applications issue I/O operations without waiting; the OS notifies completion, avoiding thread blocking and improving throughput.

3. Lightweight process/thread model

Uses coroutines or event‑driven architectures to handle many connections within a single thread, reducing context‑switch overhead.

4. Network stack optimization

Techniques such as zero‑copy, TCP window scaling, and DPDK/XDP bypass the kernel stack to accelerate packet processing.

By combining these technologies, a server can efficiently manage tens of thousands of concurrent connections.