Content deleted Content added
I added a reference to a conference paper discussing the C10M problem |
No edit summary |
||
Line 4:
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 operating system 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 operating system related), strategies implied relate to the very diverse aspects of the I/O management.<ref name=Liu-Deters />
== C10M problem ==▼
"The '''C10M''' problem relates to the classic '''C10k''' [[Internet]] [[scalability]] problem, which originally occurred in the context of ({{em|title=editor's note|1=ftp and}}) 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/blog/migratorydata-solved-the-c10m-problem/|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|author=Mihai Rotaru}}</ref>▼
<ref name="C10M-howto">{{Cite web|url=https://migratorydata.com/blog/migratorydata-with-12-million-concurrent-websockets/|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=Mihai Rotaru}}</ref>▼
<ref name="C10M-middleware-2017">{{cite journal |last1=Rotaru |first1=Mihai |last2=Olariu |first2=Florentin |last3=Onica |first3=Emanuel |last4=Rivière |first4=Etienne |display-authors= |date=December 2017 |title=Reliable messaging to millions of users with MigratoryData |url=https://arxiv.org/pdf/1712.09876.pdf |journal=Proceedings of the 18th ACM/IFIP/USENIX Middleware Conference: Industrial Track |pages=1–7 |doi=10.1145/3154448.3154449}}</ref>▼
== History ==
Line 20 ⟶ 14:
<ref name="conn-very-high-file">{{Cite book|url=https://www.google.it/books/edition/High_Performance_Computing_HiPC_2008/cNwZ1snBYQYC?hl=it&gbpv=1&dq=file+server+very+high+number+of+connections&pg=PA470&printsec=frontcover|title=High Performance Computing - HiPC 2008|language=en|year=2008|access-date=2021-10-15|author1=Ponnuswamy Sadayappan|author2=Manish Parashar|author3=Ramamurthy Badrinath|author4=Viktor K. Prasanna|isbn=978-3-540-89893-1}}</ref>
<ref name="C10M" />
▲== C10M problem ==
▲"The '''C10M''' problem relates to the classic '''C10k'''
▲<ref name="C10M">{{Cite web|url=https://migratorydata.com/blog/migratorydata-solved-the-c10m-problem/|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|author=Mihai Rotaru}}</ref>
▲<ref name="C10M-howto">{{Cite web|url=https://migratorydata.com/blog/migratorydata-with-12-million-concurrent-websockets/|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=Mihai Rotaru}}</ref>
▲<ref name="C10M-middleware-2017">{{cite journal |last1=Rotaru |first1=Mihai |last2=Olariu |first2=Florentin |last3=Onica |first3=Emanuel |last4=Rivière |first4=Etienne |display-authors= |date=December 2017 |title=Reliable messaging to millions of users with MigratoryData |url=https://arxiv.org/pdf/1712.09876.pdf |journal=Proceedings of the 18th ACM/IFIP/USENIX Middleware Conference: Industrial Track |pages=1–7 |doi=10.1145/3154448.3154449}}</ref>
== See also ==
| |||