Nodejs vs Play for Front-End Apps
subbu.org
Nodejs vs Play for Front-End Apps
1–10 of 15 posts
Re: Nodejs vs Play for Front-End Apps
#2Without 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.
Re: Nodejs vs Play for Front-End Apps
#3> 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?
Re: Nodejs vs Play for Front-End Apps
#4> 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?
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?
Re: Nodejs vs Play for Front-End Apps
#5Some 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?
Re: Nodejs vs Play for Front-End Apps
#6Without 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.
Yeah. 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.
Re: Nodejs vs Play for Front-End Apps
#7> 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?
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.
Re: Nodejs vs Play for Front-End Apps
#8Some 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...
Re: Nodejs vs Play for Front-End Apps
#9Earlier 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.
Yes, correct - I'm not able to disclose the code. But there is more to come and I will be sharing the code on github.
Re: Nodejs vs Play for Front-End Apps
#10In 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.