The C10K problem
At the start of the 21st century, engineers ran into a scalability bottleneck: web servers were not able to handle more than 10,000 concurrent connections. For example, for the Apache server, performance was inversely proportional to the number of concurrent connections. Daniel Kegel wrote a paper (http://www.kegel.com/c10k.html ) about this problem in detail, and included his tuning on how to get one web server to handle 10,000 connections.
Apache (until Version 2.4) could be configured to run in two main modes: pre-forked or worker multi-process mode (MPM). Either way, with each request that is currently active in the system, one thread is hogged up and competes for resources like CPU and memory with all other threads. ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access