News for hackers. Stuff that matters.
Re:RingoJS vs NodeJS by amix on Wednesday June 23, 2010 @12:50PM (#1455449)
Before our node.js solution we actually ran Java along with a highly optimized JBoss Netty comet implementation and it had a hard time scaling since it used _a lot_ of memory. Generally, our Java solution used around 10 times more memory than our node.js solution. Like I note in that post:

"We have rewritten to node.js from Java+JBoss Netty, because the old solution had scalability problems. We have also been able to build a very sophisticated messaging system given JavaScript expressiveness and the simplicity of node.js. Generally, we have found node.js and V8 very impressive - and it uses about 10 times less memory than Java+Netty did."

Jetty Comet uses a lot more memory than a vanilla JBoss Netty implementation - at least based on my benchmarks.

Re:RingoJS vs NodeJS by hannesw on Wednesday June 23, 2010 @01:59PM (#1455634)
I know, i read that post. I'm planning to do a Node/Ringo comet comparison soon, and memory usage/max connections will be a part of that.
Re:RingoJS vs NodeJS by praxxis on Wednesday June 23, 2010 @08:00PM (#1456873)
Please do. I don't know why people keep reposting my benchmark, its terrible and really only applied to what I'm doing with Comet. Memory, etc, isn't the biggest factor for us.