Matt, The original post started with an observation and a request for more details, presumably from those who know what's going on under the hood. I didn't detect any hint of "expecting Node to compare well with nginx or Apache."
A conversation about the underlying differences in the servers and thoughts on how or how much node can be optimized would have been welcome. Instead, your response was not only unhelpful, but condescending. Someone willing to go to the trouble of running the profiler and set up benchmarks is already aware that they could simply use nginx. Shouldn't we appreciate and support others' efforts - as it could lead directly to improvements in node? Chris On Feb 15, 2:01 pm, Matt <[email protected]> wrote: > On Wed, Feb 15, 2012 at 1:56 PM, billywhizz <[email protected]> wrote: > > i don't hear anyone on this thread complaining that node.js is slower. > > This thread started with: "I analysed node-0.6.10/windows2008r2 running my > clustered http server script in VTune with a view to understanding why node > took 50% more CPU than nginx/apache for a given scenario." > > And it's not the first time I've seen Node serving files benchmarked > against nginx. > > Matt. -- 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
