News for hackers. Stuff that matters.

A comment on Nodejs vs Play for Front-End Apps.

Re:Nodejs vs Play for Front-End Apps by vmind on Sunday March 27, 2011 @07:21PM (#2376398)
Some truly bad graphs there, displaying response time on same axis as responses per second? Leaving in a bracket probably to contain outliers and flattening the rest of the graph?
[ Parent | on HN ]
Re:Nodejs vs Play for Front-End Apps by s3u on Sunday March 27, 2011 @09:23PM (#2376692)
Point well taken - there was no such intention. I updated the charts to show req/sec and mean response time separately. See http://www.subbu.org/blog/2011/03/nodejs-vs-play-for-front-e...
[ Parent | on HN ]
Re:Nodejs vs Play for Front-End Apps by andos on Monday March 28, 2011 @08:57AM (#2378159)
How does the "Render - No IO" case work? Does it take a different code path? (E.g. render "No entries found" instead of iterating over each entry and rendering it?) Or, put differently, what are you measuring in the "Render - No IO" case?
[ Parent | on HN ]
Re:Nodejs vs Play for Front-End Apps by s3u on Tuesday March 29, 2011 @01:18PM (#2383460)
The source is now on github. See the links at the top of the blog post.
[ Parent | on HN ]