You are welcome! On Thu, Jan 23, 2014 at 7:19 PM, Alexey Petrushin <alexey.petrus...@gmail.com> wrote: > Fedor, you are right, thanks. That was the problem, after fixing it node > became more than 10 times faster. > > Issue resolved. > > > On Thursday, 23 January 2014 14:15:19 UTC+4, Fedor Indutny wrote: >> >> I think you could be hitting this: >> http://nodejs.org/api/http.html#http_agent_maxsockets >> >> On Thu, Jan 23, 2014 at 1:57 PM, Alexey Petrushin >> <alexey.p...@gmail.com> wrote: >> > I ran a benchmark for Ruby on Rails and Express.js using `siege` - and >> > Express for some reason performed worse than Rails. >> > >> > How benchmark works - application query some text from remote HTTP >> > service >> > (service delays each >> > request for 200ms) and render HTML page using that text. >> > >> > Results >> > >> > - transactions rate are the same (already strange, I expected node.js to >> > outperform rails by at least a couple of times) >> > - average response time in rails is 0.8s and in express 4s (siege >> > doesn't >> > show average time it in the report, but it can be seen from its logs). >> > >> > Details >> > >> > The remote service with delay (sipmle node.js server) >> > >> > https://github.com/alexeypetrushin/web-frameworks-benchmarks/blob/master/lorem-ipsum.js >> > >> > Express.js >> > >> > https://github.com/alexeypetrushin/web-frameworks-benchmarks/blob/master/expressjs/app.js >> > >> > Rails (with Puma server) >> > >> > https://github.com/alexeypetrushin/web-frameworks-benchmarks/blob/master/rails/app/controllers/posts_controller.rb >> > >> > Siege command `siege -b -t10s -c100 http://localhost:3000` >> > >> > Full code and instructions how to run >> > https://github.com/alexeypetrushin/web-frameworks-benchmarks >> > All application has been run in production mode. >> > >> > How is that possible and where is the bug in this benchmark, what's I'm >> > doing wrong? >> > >> > -- >> > -- >> > Job Board: http://jobs.nodejs.org/ >> > Posting guidelines: >> > 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 post to this group, send email to nod...@googlegroups.com >> > To unsubscribe from this group, send email to >> > nodejs+un...@googlegroups.com >> > For more options, visit this group at >> > http://groups.google.com/group/nodejs?hl=en?hl=en >> > >> > --- >> > 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+un...@googlegroups.com. >> > For more options, visit https://groups.google.com/groups/opt_out.
-- -- Job Board: http://jobs.nodejs.org/ Posting guidelines: 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 post to this group, send email to nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en --- 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. For more options, visit https://groups.google.com/groups/opt_out.
