Content deleted Content added
add an aosabook nginx reference and remove {{notability}}, as Kegel's c10k is very widely known concept; bold out Dan Kegel, as this concept is always credited back to him in all literature |
Jimmy Olano (talk | contribs) →History: →References: Hi everybody! I added a cite web reference, thanks for your attention! Tag: nowiki added |
||
Line 5:
== History ==
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" 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>
Line 19 ⟶ 20:
== References ==
{{Reflist |refs=▼
<ref name=aosa2:nginx>{{cite book
|author= Andrew Alexeev
Line 31 ⟶ 32:
|quote= Around ten years ago, Daniel Kegel, a prominent software engineer, … Kegel's C10K manifest … solving the C10K problem of 10,000 simultaneous connections, [[nginx]] …
}}</ref>
<ref name = "Dan Kegel, kegel.com, 1999" > {{ Cite web | url = http://www.kegel.com/c10k.html | title = The C10K problem | access-date = 18 June 2019 | first = Dan | last = Kegel | date = 8 May 1999 | website = Kegel com | quote = <nowiki>And computers are big, too. You can buy a 500MHz machine with 1 gigabyte of RAM and six 100Mbit/sec Ethernet card for $3000 or so. Let's see - at 10000 clients, that's 50KHz, 100Kbytes, and 60Kbits/sec per client. It shouldn't take any more horsepower than that to take four kilobytes from the disk and send them to the network once a second for each of ten thousand clients. (That works out to $0.30 per client, by the way. Those $100/client licensing fees some operating systems charge are starting to look a little heavy!) So hardware is no longer the bottleneck.</nowiki> | format = html | archive-url = https://web.archive.org/web/19990508164301/http://www.kegel.com/c10k.html | archive-date = 8 May 1999 | df = dmy-all }} </ref>
}}
| |||