C10k problem

From Wikipedia, the free encyclopedia
Jump to: navigation, search

The C10k problem is the problem of optimising network sockets to handle a large number of clients at the same time.[1] The name C10k is a numeronym for concurrently handling ten thousand connections.[2] 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. According to the scope of services to be made available and the capabilities of the O.S. as well as hardware considerations such as multi-processing capabilities, a multi-threading model or a single threading model can be preferred. Concurrently with this aspect which involves considerations regarding memory management (usually O.S. related), strategies implied relate to the very diverse aspects of the I/O management.[2]

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[3] nginx to solve the C10K problem)[4]
  • Lighttpd, which relies on an asynchronous architecture to handle requests[5]
  • Cherokee, a lightweight web server[6]
  • Tornado, a non-blocking web server and web application framework[7] 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[8]
  • Mojolicious, a real time web application framework written in Perl.
  • Node.js, asynchronous, non-blocking web server running on Google's V8 JavaScript engine[9]
  • 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 (web server), another very lightweight web server written in Erlang[10]
  • asyncore (in the standard Python library), a non-blocking web server library. It is based on Medusa, which is no longer maintained.
  • Shrapnel, asynchronous, high performance cooperative threading library for Python.
  • 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.[11]
  • vibe.d (web framework), a simple asynchronous I/O web framework written in D[12]
  • ribs2, event-driven fibers ("ribbons") - "blocking" code simply becomes non-blocking.
  • mcorelab, async, on the metal framework, 100k+ websockets, millions messages/s, perf numbers at c100k

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

See also[edit]

References[edit]

  1. ^ "The C10K problem". Archived from the original on 2013-07-28. 
  2. ^ a b Liu, D.; Deters, R. (2009). "The Reverse C10K Problem for Server-Side Mashups". Service-Oriented Computing – ICSOC 2008 Workshops. Lecture Notes in Computer Science 5472. p. 166. doi:10.1007/978-3-642-01247-1_16. ISBN 978-3-642-01246-4.  edit
  3. ^ Load Balancer Update
  4. ^ nginx wiki
  5. ^ Solution of lighttpd of C10k problem
  6. ^ Cherokee project server homepage
  7. ^ Tornado Web Server
  8. ^ Netty: Home (Main.WebHome)
  9. ^ node.js
  10. ^ https://github.com/extend/cowboy extend/cowboy
  11. ^ https://github.com/aaugustin/django-c10k-demo
  12. ^ http://vibed.org
  13. ^ http://maxim.livejournal.com/392971.html