Ruby - Handling 1 Million Concurrent Connections • Hacker News Board

Re: Ruby - Handling 1 Million Concurrent Connections

#61

Post by headius » Thu, Feb 21, 2013, 7:57 PM UTC

headius wrote: post #60

The author asserts that JRuby would consume more than 15GB of memory without providing any justification. Perhaps it would be better to actually try it rather than just making sweeping generalizations.

Here's a case study showing over 500k connections to a Java instance in 2.5GB of memory using NIO. JRuby's implementation of Ruby's IO is implemented directly atop NIO. So yeah...that 15GB assertion is nonsense.

http://urbanairship.com/blog/2010/08/24/c500k-in-action-at-u...

Re: Ruby - Handling 1 Million Concurrent Connections

#62

Post by slivuz » Thu, Feb 21, 2013, 8:34 PM UTC

headius wrote: post #61

headius wrote: post #60

The author asserts that JRuby would consume more than 15GB of memory without providing any justification. Perhaps it would be better to actually try it rather than just making sweeping generalizations.

Here's a case study showing over 500k connections to a Java instance in 2.5GB of memory using NIO. JRuby's implementation of Ruby's IO is implemented directly atop NIO. So yeah...that 15GB assertion is nonsense. http://urbanairship.com/blog/2010/08/24/c500k-in-action-at-u...

you right, sorry for pointless blaming, my bad, had to check it first. updating orignal post

Re: Ruby - Handling 1 Million Concurrent Connections

#63

Post by FooBarWidget » Tue, Feb 26, 2013, 7:58 PM UTC

marketer wrote: post #46

FooBarWidget wrote: post #44

Earlier quoted context omitted.

I/O is handled through EventMachine, not the normal Ruby I/O calls, and can therefore scale arbitrarily.

It is a little worrying that if some (perhaps inexperienced) developer arbitrarily calls a method that invokes Ruby's select, the process will crash mysteriously.

It won't crash. On many platforms, Ruby uses special select() hacks to extend the number of file descriptors select() can handle. On OS X it can apparently handle 10556 file descriptors. If you go over that, Ruby apparently simulates an EMFILES error.