> > Why are people expecting Node to compare well with nginx or Apache for > serving static files? Node is faster than PHP or Ruby, but comparing it to > something specifically designed for high performance static file serving is > always going to be a losing proposition. > > Use Node for your dynamic content. Use nginx or apache for your static > content. It's a very simple equation. > > > Atleast on Windows, neither nginx nor Apache is a clear winner for serving static files. Nginx native Windows version just does not scale and it is limited to 1024 concurrent connections. The cygwin version works well upto ~2000 concurrent connections. The official 32-bit Apache supports ~3000 concurrent connections but it needs a thread for each connection.
In comparison Node supports 3x/4x the Apache limit (if there are enough workers). The only downside I saw was the somewhat higher CPU usage. Looking at the Node I did not see a particular reason for the higher CPU especially since AIO/IOCP is supported. This is why I tried VTune. But looking at the VTune numbers I was unable to conclude if there was sth bad or if sth could be changed to reduce CPU. -- -- 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
