News for hackers. Stuff that matters.
Re:Vert.x (JVM async) vs Node.js Http benchmarks results by DTrejo on Wednesday May 09, 2012 @05:57PM (#3950687)
The streaming node.js example he wrote uses a blocking call. This is not the node way, and would cause a definite slow-down.

If you're worried about your programs containing rogue & misbehaving code like this, I recommend you use https://github.com/isaacs/nosync

Re:Vert.x (JVM async) vs Node.js Http benchmarks results by nfriedly on Wednesday May 09, 2012 @07:33PM (#3951062)
I had the impression that "Node.js (readfile)", and possibly "Node.js" meant the blocking call but that "Node.js (streams)" meant he was using something like fs.createReadStream(). But you're right, I don't see that anywhere in the posted source.
Re:Vert.x (JVM async) vs Node.js Http benchmarks results by purplefox on Thursday May 10, 2012 @05:04AM (#3952479)
I've tested several combinations of blocking, non blocking, readFile, streams (pipe) and using chunked transfer encoding.

Results vary a little but all way below the Vert.x results.

See blog post for the stats.

Re:Vert.x (JVM async) vs Node.js Http benchmarks results by nfriedly on Thursday May 10, 2012 @04:44PM (#3955925)
Fair enough. After I wrote that I remembered that readFile wasn't blocking anyways, but it was too late to edit at that point.