Ruby - Handling 1 Million Concurrent Connections
1–10 of 63 posts
Re: Ruby - Handling 1 Million Concurrent Connections
#2I have done this before using Java 7 async nio. The performance would drop like a brick when data received actually needed some sort of processing. How does this implementation hold up when you need to perform a O(n) operation on received data? Experiment with different sizes of n to see how the performance holds up.
Re: Ruby - Handling 1 Million Concurrent Connections
#3Good job...
You can also open 1 million connections using one linux box a) increase local port range 1024 to 65535 b) setup 17 ip address. c) open from each ip address 58824 connections
Re: Ruby - Handling 1 Million Concurrent Connections
#4Good job... You can also open 1 million connections using one linux box a) increase local port range 1024 to 65535 b) setup 17 ip address. c) open from each ip address 58824 connections
sure, i tried, but connections comes slow...
i wanted they to come like a tornado.
Re: Ruby - Handling 1 Million Concurrent Connections
#5Good job... You can also open 1 million connections using one linux box a) increase local port range 1024 to 65535 b) setup 17 ip address. c) open from each ip address 58824 connections
What would be the point of that? The bottleneck here is not the amount of ports. TCP can handle concurrency over one single input port just fine.
The issue here is concurrency on the service software. If you have to launch a million instances to listen on a million different ports, you are doing it wrong.
Re: Ruby - Handling 1 Million Concurrent Connections
#6I have to ask, is there even a practical purpose for this? Is there even some remote screwball application for having to have one machine handle 1,000,000 requests? One of the things I like about coming to HN is that the items on the front page are often actionable pieces of advice or clever and interesting hacks. I don't feel that "$LANG can do $LARGE_NUMBER of things" fits the bill. For example:
C - Handling 1 Million Concurrent Connections
Java - Handling 1 Million Concurrent Connections
Javascript - Handling 1 Million Concurrent Connections
Go - Handling 1 Million Concurrent Connections
Re: Ruby - Handling 1 Million Concurrent Connections
#7For JRuby Streaming I have used Torquebox (JBoss) successfully.
Re: Ruby - Handling 1 Million Concurrent Connections
#8I have to ask, is there even a practical purpose for this? Is there even some remote screwball application for having to have one machine handle 1,000,000 requests? One of the things I like about coming to HN is that the items on the front page are often actionable pieces of advice or clever and interesting hacks. I don't feel that "$LANG can do $LARGE_NUMBER of things" fits the bill. For example: C - Handling 1 Mill…
start with Ruby as backend for online games...
continue with Ruby as backend for audio/video chats...
consider Ruby for streaming podcasts...
etc. etc.
Re: Ruby - Handling 1 Million Concurrent Connections
#9I have to ask, is there even a practical purpose for this? Is there even some remote screwball application for having to have one machine handle 1,000,000 requests? One of the things I like about coming to HN is that the items on the front page are often actionable pieces of advice or clever and interesting hacks. I don't feel that "$LANG can do $LARGE_NUMBER of things" fits the bill. For example: C - Handling 1 Mill…
WhatsApp had over 2 million users connected to their (Erlang) server last year.
http://blog.whatsapp.com/index.php/2012/01/1-million-is-so-2...
Here is the same in Erlang for reference (from a few years ago, I would be interested to see if there is a more efficient way now):
http://www.metabrew.com/article/a-million-user-comet-applica...
Re: Ruby - Handling 1 Million Concurrent Connections
#10I have to ask, is there even a practical purpose for this? Is there even some remote screwball application for having to have one machine handle 1,000,000 requests? One of the things I like about coming to HN is that the items on the front page are often actionable pieces of advice or clever and interesting hacks. I don't feel that "$LANG can do $LARGE_NUMBER of things" fits the bill. For example: C - Handling 1 Mill…
What happens when one of the fully loaded 1 million connection nodes goes bang? That's potentially a million users getting a poor experience.
Re-establishing a million connections at once is going to be hard on the network - the million were built up over a period of time previously yet now they're being re-established Big Bang style.