I didn't know about this either, good info. Is there a good method for determining what the optimum # max connections should be? I assume there's some practical limit, or way of figuring out the point of diminishing returns for a given app? for example, if you open up (as the OP did) 1000 concurrent connections, but your db connection pool is only 10, then you're probably going to run into issues. Other than dependencies like that, any good rubrics y'all can think of?
On Thursday, January 23, 2014 5:15:19 AM UTC-5, 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 > <[email protected] <javascript:>> 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 [email protected]<javascript:> > > To unsubscribe from this group, send email to > > [email protected] <javascript:> > > 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 [email protected] <javascript:>. > > 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 [email protected] To unsubscribe from this group, send email to [email protected] 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 [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
