Re:Deft server (Java) beats Node.js and Tornado
by davesims on Monday February 20, 2012 @01:59AM
(#3611596)
"Tornado and Node.js are the two other asynchronous web servers that we used in the benchmark. We didn't include Netty because it felt a little bit like comparing apples with oranges. But I wouldn't doubt if Netty showed numbers equal to (or greater?) the results we have seen for Deft. Netty, the successor to apache mina, is a really cool socket framework written by a really smart guy (Trustin Lee)."
Re:Deft server (Java) beats Node.js and Tornado
by spullara on Monday February 20, 2012 @02:00AM
(#3611599)
So, first of all this is hosted on Google App Engine -- so I don't even see how it could even provide what is claimed. The environment doesn't really support it.
If you want asynchronous network programming in Java or Scala, you should be using either Netty or something higher level like Finagle: http://github.com/twitter/finagle
Re:Deft server (Java) beats Node.js and Tornado
by Uchikoma on Monday February 20, 2012 @01:59AM
(#3611597)
I'd assume classes of web app servers perform roughly the same. An evented server in C(++) (Nodejs) should be faster than an evented server in Java for small app code request handlers.
For larger app code the speed should approach the performance ratio of the VMs (V8/JVM) involved.
In the meantime, Google returns this article about it: http://www.infoq.com/articles/deft-loft
The example code shown does nothing that Netty can't do without using any external "frameworks".
If you want asynchronous network programming in Java or Scala, you should be using either Netty or something higher level like Finagle: http://github.com/twitter/finagle
For larger app code the speed should approach the performance ratio of the VMs (V8/JVM) involved.
So I think this is rather uninteresting.