>>> Also, run a caching proxy if at all possible. That made the single >>> biggest difference for my server. >>> >>> Other useful things: >>> * Set the MaxRequestsPerChild to something like 450. >> >> That's pretty low. You'd barely get your application parsed, cached, >> and load some data before you'd have to recycle the child process. Most >> people set it around 10000. Large enough to be useful, but still deal with >> any minor memory leaks. > > Depends on your application. I had to set it low because the > application wouldn't fit in a 540MB VPS, otherwise. I've since bumped > up to a 2GB VPS, so I can probably afford Really, a caching proxy is > the first, best thing, if it's not already in use. > > Let the thread carry on...
A cache makes sense, but I hesitate to establish a new layer. How is the setup and maintenance? I found this which is at least not super-easy: http://www.apachetutor.org/admin/reverseproxies Would I be able to make a change to an image, immediately refresh, and see the change? - Grant
