C10k problem

From Wikipedia, the free encyclopedia
Jump to: navigation, search
This article has multiple issues. Please help improve it or discuss these issues on the talk page.
This article has an unclear citation style. The references used may be made clearer with a different or consistent style of citation, footnoting, or external linking. Violates Wikipedia:External links: "Wikipedia articles may include links to web pages outside Wikipedia (external links), but they should not normally be used in the body of an article.". (January 2013)
Question book-new.svg
 This article relies on references to primary sources. Please add references to secondary or tertiary sources. (January 2010)

The C10k problem[1] refers to the problem of optimising socket server software to handle a large number of clients at the same time (hence the name C10k - concurrent ten thousand connections). The problem of socket server optimisation has been studied because a number of factors must be considered to allow a web server to support many clients. This can involve a combination of operating system constraints and web server software limitations.[further explanation needed]

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.

The problem's name is a numeronym for "ten thousand clients".[1]

Contents

Servers which address the problem [edit]

Several web servers have been developed to counter the C10K problem:

  • nginx, which relies on an event-driven (asynchronous) architecture, instead of threads, to handle requests (WordPress.com uses[2] nginx to solve the C10K problem)[3]
  • Lighttpd, which relies on an asynchronous architecture to handle requests[4]
  • Cherokee, a lightweight web server[5]
  • Tornado, a non-blocking web server and web application framework[6] written in Python (used by Facebook's FriendFeed)
  • Apache AWF (retired, formerly Apache Deft), asynchronous, non-blocking web server running on the JVM
  • JBoss Netty, a NIO client server framework which enables quick and easy development of network applications such as protocol servers and clients[7]
  • Node.js, asynchronous, non-blocking web server running on Google's V8 JavaScript engine[8]
  • EventMachine, an asynchronous, non-blocking web server running on Ruby EventMachine
  • Yaws, a web server written in Erlang; profiting from Erlang's extremely lightweight processes.
  • Cowboy, an other, very lightweight, web server written in Erlang[9]
  • asyncore (in the standard Python library), a non-blocking web server library. It is based on Medusa, which is no longer maintained.
  • IIS, Microsoft's flagship web server, through the use of asynchronous requests, as demonstrated by third-party components such as WebSync
  • Jetty asynchronous Java servlet container
  • pyftpdlib, an extremely fast and scalable FTP server written in Python
  • Xitrum, an async and clustered Scala web framework and HTTP(S) server based on Netty
  • Django, some research is being done using the asynchronous IO support in Python 3.3.[10]
  • Vibe.d, a simple asynchronous I/O web framework written in D[11]

There is a benchmark done for comparing the performance of various web frameworks supporting c10k solutions.[12]

See also [edit]

References [edit]

  1. ^ a b The C10K problem
  2. ^ Load Balancer Update
  3. ^ nginx wiki
  4. ^ Solution of lighttpd of C10k problem
  5. ^ Cherokee project server homepage
  6. ^ Tornado Web Server
  7. ^ Netty: Home (Main.WebHome)
  8. ^ node.js
  9. ^ extend/cowboy · GitHub
  10. ^ [1]
  11. ^ [2]
  12. ^ http://maxim.livejournal.com/392971.html

External links [edit]


Stub icon This World Wide Web-related article is a stub. You can help Wikipedia by expanding it.
Retrieved from "http://en.wikipedia.org/w/index.php?title=C10k_problem&oldid=552624957"