C10k problem: Difference between revisions

Revision as of 15:43, 24 July 2017

Revision as of 16:31, 3 August 2017

Line 4:

== History ==

The term was coined in 1999 by Dan Kegel, citing the [[Simtel]] FTP host, [[cdrom.com]], serving 10,000 clients at once over 1 Gigabit[[gigabit per second]] [[Ethernet]] in that year.<ref name="C10K" /> The term has since been used for the general issue of large number of clients, with similar numeronyms for larger number of connections, most recently [[C10M]] in the 2010s.<ref name=":0" />

By the early 2010s millions of connections on a single commodity 1U server became possible: over 2 million connections ([[WhatsApp]], 24 cores, using [[Erlang (programming language)|Erlang]] on [[FreeBSD]]),<ref>[http://blog.whatsapp.com/196/1-million-is-so-2011 1 million is so 2011]</ref><ref>[http://www.erlang-factory.com/upload/presentations/558/efsf2012-whatsapp-scaling.pdf Scaling to Millions of Simultaneous Connections], Rick Reed, ''WhatsApp''</ref> 10–12 million connections (MigratoryData, 12 cores, using [[Java (Programming language)|Java]] on [[Linux]])<ref name=":0">[https://mrotaru.wordpress.com/2015/05/20/how-migratorydata-solved-the-c10m-problem-10-million-concurrent-connections-on-a-single-commodity-server/ How MigratoryData solved the C10M problem: 10 Million Concurrent Connections on a Single Commodity Server]</ref><ref>[https://mrotaru.wordpress.com/2013/10/10/scaling-to-12-million-concurrent-connections-how-migratorydata-did-it/ Scaling to 12 Million Concurrent Connections: How MigratoryData Did It]</ref>