Those sure are some misleading bar charts.
Nodejs vs Play for Front-End Apps
11–15 of 15 posts
Re: Nodejs vs Play for Front-End Apps
#12Some 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?
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...
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?
Re: Nodejs vs Play for Front-End Apps
#13Those sure are some misleading bar charts.
What's misleading about them?
Please feel free to reproduce on your own. The source is on github. See the blog post for github links.
Re: Nodejs vs Play for Front-End Apps
#14Earlier quoted context omitted.
That also caught my eye, I thought this is either some prolific 2 hour work or there is some sort of bias he doesn't want us to know about?
It is kind of odd, but at the beginning of the article he states that he originally wrote and did the tests as part of his work at Ebay.
The source is now on github. See the blog post for github links.
Re: Nodejs vs Play for Front-End Apps
#15Earlier quoted context omitted.
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...
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?
The source is now on github. See the links at the top of the blog post.