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

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.