Thank you Shripad and Tim for showing where the bottleneck is. I'm accepting Shripad's answer on Stackoverflow as well. You people rock!
On Wednesday, August 15, 2012 4:24:57 PM UTC+6, MHK wrote: > > Being both event-driven servers, why node.js needs async code where Nginx > doesn't? In another words, if Nginx works as the same event-driven async IO > model of node, why doesn't it requires writing async style code? I know, > Nginx is *NOT* actually executing any code, rather proxying them to who > can. Then why doesn't node do so? Are we missing anything in the current > Ngninx way? Or, gaining anything more from node (apart from the pain of > writing async codes)? > > To be more specific, how different is Nginx+php-fpm or > Nginx+wsgi+python/ruby from node alone regarding performance or utilizing > computing resource that node claims? Couldn't node just use existing > FastCGI models, be a sync style JavaScript interpreter and let webserver do > its async job? > > PS. This question is cross-posted in > stackoverflow<http://stackoverflow.com/questions/11966292/being-both-event-driven-servers-why-node-js-needs-async-code-where-nginx-doesn> > . > -- 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
