Both Apache and Nginx depend on an external services for running rails so speed their depends on that service.
In most setups you are only using Apache or Nginx as a proxy to that service, and to serve up static assets. As Nginx (as everyone else has mentioned) is considered to be lighter weight, running faster ,in less memory but with some sacrifice of (advanced) functionality it is generally considered to be the better partner to what ever is running rails, after all you don't need a lot of the functionality Apache traditionally offers. My personal preference is for Nginx for static files and proxy duties and Unicorn for running rails :) On 11 Aug, 14:09, Will Jessop <[email protected]> wrote: > On Wed, Aug 11, 2010 at 1:15 PM, Francis Fish <[email protected]> wrote: > > On Wed, Aug 11, 2010 at 12:58 PM, Will Jessop <[email protected]> wrote: > >> I recommend nginx for speed, memory footprint, CPU use, ease of > >> configuration and ability to handle traffic. Think I got everything :) > > > From what I remember the Rails stack wasn't quicker but static assets > > much faster? So it depends on where the app spends most of its time. > > Rails isn't any quicker with it, but using up less resources on your > servers to do the same thing will give the other processes (such as > Rails) more space to play. > > Will. > > -- > Will Jessop > Super Shiny Robot Limited - Professional web design and development > > t: 07939 547 962 > w:http://supershinyrobot.com/ -- You received this message because you are subscribed to the Google Groups "NWRUG" 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/nwrug-members?hl=en.
