C10k problem: Difference between revisions

Revision as of 11:04, 15 October 2021

Revision as of 11:27, 15 October 2021

Line 7:

== C10M problem ==

"The '''C10M''' problem relates to the classic '''C10k''' [[Internet]] [[scalability]] problem, which originally occurred in the context of web servers. The C10M problem, which consists in supporting 10 million concurrent connections on a single machine, remains a challenging problem not only for web servers, but for any [[Server (computing)|Internet server]] in general."

<ref name="C10M">{{Cite web|url=https://migratorydata.com//2015/05/20/how-migratorydata-solved-the-c10m-problem-10-million-concurrent-connections-on-a-single-commodity-server/|title=How MigratoryData solved the C10M problem: 10 Million Concurrent Connections on a Single Commodity Server|website=migratorydata.com|language=en|date=2015-05-20|access-date=2021-10-15|author1=Unknown|author2=Robert Graham}}</ref>

<ref name="C10M" />

<ref name="C10M-howto">{{Cite web|url=https://migratorydata.com/2013/10/10/scaling-to-12-million-concurrent-connections-how-migratorydata-did-it/|title=Scaling to 12 Million Concurrent Connections: How MigratoryData Did It|website=migratorydata.com|language=en|date=2013-10-10|access-date=2021-10-15|author=Unknown}}</ref>

== History ==

Line 13 ⟶ 14:

The term was coined in 1999 by '''Dan Kegel''',{{r|aosa2:nginx}}<ref name = "Dan Kegel, kegel.com, 1999" /> citing the [[Simtel]] FTP host, [[cdrom.com]], serving 10,000 clients at once over 1 [[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 problem|C10M]]" in the 2010s.<ref name="C10M" />

By the early 2010s millions of connections on a single commodity 1U rackmount server became possible: over 2 million connections ([[WhatsApp]], 24 cores, using [[Erlang (programming language)|Erlang]] on [[FreeBSD]]),<ref name = "WhatsApp blog, 2012" > {{ Cite web | url = https://blog.whatsapp.com/196/1-million-is-so-2011 | title = 1 million is so 2011 | access-date = 25 July 2019 | date = 6 January 2012 | website = [[WhatsApp]] blog | quote = This time we also wanted to share some more technical details with you about hardware, OS and software: hw.machine: amd64 hw.model: Intel(R) Xeon(R) CPU X5675 @ 3.07GHz hw.ncpu: 24 hw.physmem: 103062118400 hw.usermem: 100556451840 | archive-url = https://web.archive.org/web/20140501234954/https://blog.whatsapp.com/196/1-million-is-so-2011 | archive-date = 1 May 2014 | df = dmy-all }} </ref><ref name = "Reed, Erlang Factory, 2012" > {{ Cite web | url = http://www.erlang-factory.com/upload/presentations/558/efsf2012-whatsapp-scaling.pdf | title = Scaling to Millions of Simultaneous Connections | access-date = 25 July 2019 | first = Rick | last = Reed | date = 30 March 2012 | website = Erlang Factory | format = pdf | page = 7 | archive-url = https://web.archive.org/web/20120709235656/http://www.erlang-factory.com/upload/presentations/558/efsf2012-whatsapp-scaling.pdf | archive-date = 9 July 2012 | df = dmy-all }} </ref> 10–12 million connections (MigratoryData, 12 cores, using [[Java (Programming language)|Java]] on [[Linux]]).<ref name="C10M">[https://migratorydata.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://migratorydata.com/2013/10/10/scaling name="C10M-to-12-million-concurrent-connections-how-migratorydata-did-it/howto" Scaling to 12 Million Concurrent Connections: How MigratoryData Did It]</ref>

Common applications of very high number of connections include pub/sub servers, chat, file servers, web servers, and software-defined networking.{{citation needed|reason=examples given are non-obvious and need justification.|date=July 2015}}