However, comparing naive approaches with different utilities like these does have its warrant. Lets please not ignore that. Technically it may be apples vs. oranges but from a user perspective it is not. It is comparing how well you App does after you spend say an afternoon or weekend getting comfortable with either toolchain and doing your thing.
After all this is what users wanting to concentrate on inventing something often do. They don't want to spend their time on complicated issues to squeeze out the last bit, they just get these basic things done as fast as possible while making their inventive contribution on the plane on it. And if a naive 2 liner in php performs better unless you someone tells you, you gotta use a pool module and you gotta use a cluster module and and and in node, this is also a statement for both toolchains. After all, this is what both tool chains are about first place compared to doing a heavy C(++) implementation, getting things developed rapidly. And even with that, you'd also have to fine tune the native thing a lot, like using hashtables, while using either PHP or Node you get them free of the box, thus you might perform better than using a naive C++ application. On Mon, Mar 2, 2015 at 5:22 PM, Matt <hel...@gmail.com> wrote: > That Node vs Rails benchmark is also broken for almost exactly the same > reasons your benchmark is broken: It doesn't use cluster, and it uses the > default Node.js "Agents" limitation on outgoing HTTP requests (which will > only do 5 in parallel). > > You want a real-world example? I ported a Rails application to Node.js and > it got significantly faster. A real full-blown app. Everything felt faster > to our users. That's the only benchmark that matters. I did benchmark some > endpoints and they went from around 100rps to around 1000rps, but just > testing one endpoint doesn't really matter - you need to get a feel for the > entire app. > > Matt. > > On Sun, Mar 1, 2015 at 4:27 AM, Alexey Petrushin < > alexey.petrus...@gmail.com> wrote: > >> Also, if you are interested in "kinda real-life" Node.js benchmarks, >> here's one more for Ruby on Rails vs Node.js >> >> http://jslang.info/blog/2014/ruby-on-rails-vs-nodejs >> >> 3782 (node.js) vs. 2914 (ruby on rails) hits >> >> >> On Thursday, 19 February 2015 08:34:57 UTC+11, Anirban Bhattacharya wrote: >>> >>> Hi, >>> I am new to node. very new ..like infant. >>> Either I am doing something wrong or I understood everything wrong. >>> I wrote a node js simple JSON emitter which uses mysql module and query >>> (select *) from a single table haviing 100 records and outputs on page as >>> JSON (JSON.stringify.. >>> >>> I wrote a PHP page which also does the same thing from same >>> table(Apache). >>> >>> I used Siege for load test and surprisingly it shows better values for >>> the PHP than that of node .. see below the output of siege >>> ==================NODE================= >>> anirbanb2004@Anisoft-Corporation:~$ siege -c100 -d1 -t10M -lnode.log >>> http://localhost:9615/ >>> ** SIEGE 3.0.5 >>> ** Preparing 100 concurrent users for battle. >>> The server is now under siege... >>> Lifting the server siege... done. >>> >>> Transactions: 119236 hits >>> Availability: 100.00 % >>> Elapsed time: 599.74 secs >>> Data transferred: 403.00 MB >>> Response time: 0.00 secs >>> Transaction rate: 198.81 trans/sec >>> Throughput: 0.67 MB/sec >>> Concurrency: 0.61 >>> Successful transactions: 119236 >>> Failed transactions: 0 >>> Longest transaction: 0.05 >>> Shortest transaction: 0.00 >>> >>> FILE: node.log >>> =================PHP================== >>> anirbanb2004@Anisoft-Corporation:~$ siege -c100 -d1 -t10M -lphp.log >>> http://localhost/loadTest >>> ** SIEGE 3.0.5 >>> ** Preparing 100 concurrent users for battle. >>> The server is now under siege... >>> Lifting the server siege... done. >>> >>> Transactions: 119632 hits >>> Availability: 100.00 % >>> Elapsed time: 599.47 secs >>> Data transferred: 34.58 MB >>> Response time: 0.00 secs >>> Transaction rate: 199.56 trans/sec >>> Throughput: 0.06 MB/sec >>> Concurrency: 0.12 >>> Successful transactions: 59858 >>> Failed transactions: 0 >>> Longest transaction: 0.03 >>> Shortest transaction: 0.00 >>> >>> FILE: php.log >>> >>> can anyone please help me understand what is wrong here? I understand >>> some scenario will be there where PHP will perform better. What scenario >>> should I create to test Node is better? >>> >> -- >> Job board: http://jobs.nodejs.org/ >> New group rules: >> https://gist.github.com/othiym23/9886289#file-moderation-policy-md >> Old group rules: >> https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines >> --- >> You received this message because you are subscribed to the Google Groups >> "nodejs" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to nodejs+unsubscr...@googlegroups.com. >> To post to this group, send email to nodejs@googlegroups.com. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/nodejs/f272d221-954b-4aac-bcf6-fe3fb86f10a4%40googlegroups.com >> <https://groups.google.com/d/msgid/nodejs/f272d221-954b-4aac-bcf6-fe3fb86f10a4%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> >> For more options, visit https://groups.google.com/d/optout. >> > > -- > Job board: http://jobs.nodejs.org/ > New group rules: > https://gist.github.com/othiym23/9886289#file-moderation-policy-md > Old group rules: > https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines > --- > You received this message because you are subscribed to the Google Groups > "nodejs" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to nodejs+unsubscr...@googlegroups.com. > To post to this group, send email to nodejs@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/nodejs/CAPJ5V2aW_GBRUif%3Di6Hg6KyXXJP5AxBXgE51xsrdFWHf2JmDrA%40mail.gmail.com > <https://groups.google.com/d/msgid/nodejs/CAPJ5V2aW_GBRUif%3Di6Hg6KyXXJP5AxBXgE51xsrdFWHf2JmDrA%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- Job board: http://jobs.nodejs.org/ New group rules: https://gist.github.com/othiym23/9886289#file-moderation-policy-md Old group rules: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines --- You received this message because you are subscribed to the Google Groups "nodejs" group. To unsubscribe from this group and stop receiving emails from it, send an email to nodejs+unsubscr...@googlegroups.com. To post to this group, send email to nodejs@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/nodejs/CABg07fu1tCnNjDxVat94APbHJwV1SSXyThNg4mD%2BR1qYOOyNpg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
