News for hackers. Stuff that matters.
Re:We switched to Node.js: the good and the not so good by nivertech on Monday January 14, 2013 @08:42AM (#5054568)
I think the reason they only got 25% gain is because they already used Async IO with Ruby eventmachine.

Another reason might be, that their workload is IO-bounded, so faster VM like V8 doesn't help.

Re:We switched to Node.js: the good and the not so good by jahewson on Monday January 14, 2013 @09:22AM (#5054709)
If the initial version was IO-bound wouldn't they get a 0% gain from re-writing?
Re:We switched to Node.js: the good and the not so good by diroussel on Monday January 14, 2013 @09:37AM (#5054770)
If my program reads a file one byte at a time, and it's IO-bound, can I improve performance by re-writing?
Re:We switched to Node.js: the good and the not so good by jahewson on Thursday January 17, 2013 @12:39PM (#5073839)
Then it's not really IO-bound is it? It's stupidity-bound. Once you re-write it properly then it'll be IO-bound.