On 06/03/2013 22:59, Michael Mol wrote: > On 03/06/2013 03:54 PM, Grant wrote: >> I lowered my MaxClients setting in apache a long time ago after >> running out of memory a couple times. I recently optimized my >> website's code and sped the site way up, and now I find myself >> periodically up against MaxClients. Is a RAM upgrade the only >> practical way to solve this sort of problem? > > Use a reverse proxy in caching mode. > > A request served up by the proxy server is a request not served up by > Apache. > > Squid, nginx and varnish are all decent for the purpose, though squid > and nginx are probably the more polished than varnish. >
Grant, If you optimized the site well, I would imagine your RAM needs per page request would go down and you could possibly increase MaxClients again. Have you given it a try since the optimization? Increase it slowly bit by bit comparing the current performance with what it used to be, and make your judgement call. Is there some reason why you can't just add more memory to the server? It's a fast and very cheap and very effective performance booster with very little downtime. But if your slots are full and you need new hardware, that's a different story. Michael's proxy suggestion is excellent too - I use nginx for this a lot. It's amazingly easy to set up, a complete breath of fresh air after the gigantic do-all beast that is apache. Performance depends a lot on what your sites actually do, if every page is dynamic with changing content then a reverse proxy doesn't help much. Only you know what your page content is like. -- Alan McKinnon alan.mckin...@gmail.com
