4 ms·
Nodejs vs Play for Front-End Apps
- justinsb 16y agoWithout publishing the complete source for each test, these benchmarks are not very useful (the author does promise to publish sources for a new test in future). It appears that initially node.js was in 'development mode', so presumably the post initially showed Play beating node. With unreproducible benchmarks there are inevitably configuration errors made, or configuration tweaks that aren't applied.
- andos 16y agoYeah. And it's Java and all but I think there is something pretty odd if the mean time per request for Play is 1.5 seconds.
- no7hing 16y ago> I’m unable to make the source code for the test apps available publicly at this time. and > I spent nearly equal amounts of time (under two hours) to build the same app on nodejs and Play. One actually wonders: why?
- vmind 16y agoSome 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?
- s3u 16y agoPoint 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-end-apps http://www.subbu.org/blog/2011/03/nodejs-vs-play-for-front-e...
- andos 16y agoHow 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?
- s3u 16y agoThe source is now on github. See the links at the top of the blog post.
- mooftard 16y agoIn Play did you set application.mode=prod in conf/appliction.conf? If you don't do that then you're measuring something that doesn't matter to anyone.
- ShardPhoenix 16y agoThose sure are some misleading bar charts.
- s3u 16y agoWhat's misleading about them? Please feel free to reproduce on your own. The source is on github. See the blog post for github links.