On 28 April 2013 00:18, Andy Smith <andy@???> wrote:
> Hi Chris,
>
> Once you've gone as far with that as you can reasonably go, and once
> you're sure it's not some unrelated software or an application
> problem, the next scaling step is normally to put a lightweight
> reverse proxy in front of Apache.
>
> Popular reverse proxies are Nginx and Lighttpd. They accept the
> client connections, generally aggressively cache and answer from
> there where possible, refer back to an app server backend
> (Apache+Wordpress) only when necessary. You try to make sure that
> all static content is being cached so Apache never gets consulted
> for images, css etc.
>
> There are tons of guides on fronting Apache with Nginx or Lighttpd
> for this purpose.
If you are adding nginx or lighttpd, why not add them as a replacement to
apache rather than just sitting in front of it? Both a better solutions if
you want a low resource web server that scales better than apache does.
--
Michael Daffin <james1479@???>
--
Please post to: Hampshire@???
Web Interface:
https://mailman.lug.org.uk/mailman/listinfo/hampshire
LUG URL:
http://www.hantslug.org.uk
--------------------------------------------------------------
