C10k problem: Difference between revisions
Appearance
Content deleted Content added
numeronym |
|||
Line 1: | Line 1: | ||
{{primarysources|date=January 2010}} |
{{primarysources|date=January 2010}} |
||
The '''C10k problem'''<ref>[http://www.kegel.com/c10k.html The C10K problem]</ref> is the |
The '''C10k problem'''<ref>[http://www.kegel.com/c10k.html The C10K problem]</ref> is the [[numeronym]] given to a limitation that most [[web server]]s currently have which limits the web server's capabilities to only handle about ten thousand simultaneous connections. This limitation is partly due to operating system constraints and software limitations. |
||
While there are some specialized web servers that can handle more than ten thousand client connections, most web servers currently handle at most ten thousand clients simultaneously. |
While there are some specialized web servers that can handle more than ten thousand client connections, most web servers currently handle at most ten thousand clients simultaneously. |
Revision as of 22:21, 5 October 2010
The C10k problem[1] is the numeronym given to a limitation that most web servers currently have which limits the web server's capabilities to only handle about ten thousand simultaneous connections. This limitation is partly due to operating system constraints and software limitations.
While there are some specialized web servers that can handle more than ten thousand client connections, most web servers currently handle at most ten thousand clients simultaneously.
Servers for attacking C10K problem
A few web servers have been developed to counter the C10K problem:
- Nginx, that relies on an event-driven (asynchronous) architecture, instead of threads, to handle requests (WordPress.com uses NginX to solve the C10K problem)[2]
- Lighttpd, that relies on an asynchronous architecture to handle requests[3]
- Cherokee HTTP Server, a lightweight web server[4]
- Tornado (web server), a non-blocking web server and web application framework[5]