-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 02/09/2013 05:36 AM, Adam Carter wrote: > > There are several things you can do to improve the state of > things. The first and foremost is to add caching in front of the > server, using an accelerator proxy. (i.e. squid running in > accelerator mode.) In this way, you have a program which receives > the user's request, checks to see if it's a request that it already > has a response for, checks whether that response is still valid, > and then checks to see whether or not it's permitted to respond on > the server's behalf...almost entirely without bothering the main > web server. This process is far, far, far faster than having the > request hit the serving application's main code. > > > > I was under the impression that Apache coded sensibly enough to > handle incoming requests as least as well as Squid would. Agree > with everything else tho.
Sure, so long as Apache doesn't have any additional modules loaded. If it's got something like mod_php loaded (extraordinarily common), mod_perl or mod_python (less common, now) then the init time of mod_php gets added to the init time for every request handler. > OP should look into what's required on the back end to process > those 6 requests, as it superficially appears that a very small > number of requests is generating a huge amount of work, and that > means the site would be easy to DoS. Absolutely, hence the steps I outlined to reduce or optimize backend processing. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJRFlRSAAoJED5TcEBdxYwQ7BwH/Aj3hgQgGjzBoQhlZqPKDzEW pZJJVcVf4CF4sk88el8X/hPMfx2cTpuM53tLDsv3KGR1dwjP48O2oiiTubH/HRxI lNR5I22QK2YEbLzeRTZN+pkpGnyA1W+d3kF7F9aiNXVUV8KyuyxSxx+7Xm1tRW/W xcNhSLTQIpyTAx+R9MGNkJFs0gFGFgIMML4bfi5BpIrbeeVWsoe1C0syFF+HIFWP WZRtsCFhdWrZkvKUYIBkoFq9VKkSTt13eIvrPjxFUVJwFSmntxSgfqiaZxfHXp5A oSLtyz0vR6qByoivkuilNK7sI3fK8fHA0q4XF1AUaOuwcHg9AFG9pCFBUF2KOgk= =R/kD -----END PGP SIGNATURE-----
