Reply from my host (Pair) –
We just attempted to re-enable the site with CBAND enabled; CBAND
throttles incoming traffic essentially. However, even with this enabled, your site consumes way too many resources to be re-enabled at this time, as load shot up to over 50 immediately after enabling the site.
One problem that I see is that you are using php-cgiwrap on the entire
site; please note that running PHP as CGI is a lot more resource intensive and will definitely cause problems under the traffic you are seeing.
However, I even tried commenting the necessary lines ouur of your
.htaccess file; after re-enabling the domain, load was immediately back up over 30, so it is clear that a large part of the problem is the site
software/configuration itself combined with the amount of traffic you are receiving.
Unforuntely, while WP-Super-Cache does help in many instances, when
configured properly, it doesn’t always prove to be a singular fix;
there may be other problematic plugins or you may need to re-examine
your caching implementation.
Does this mean my server sucks, or is there something else I can do? The reason I have that wrap thing on is because wordpress won’t do automatic updates without it.
Thanks!
I looked at those and all the gzip tests work fine for me, so I guess it’s correctly set up. SuperCache just did nothing to help in yesterday’s digg hit. The site was down in minutes.
I just spent a bunch of money upgrading to a new server and I guess I just have to cross my fingers that next time it will roll smoothly.
Is there anything else I can do to definitively prove that my lousy hosting environment was the cause? (This was a cheap shared hosting environment) Like those testing websites represented in the other threads?
I am having similar issues with WP sites hosted at pair.com. Overall, I’ve had a long, good run with pair. But, this php-cgiwrap and memory issue. I have had similar responses from pair about using php-cgiwrap. However, I’m skittish about not running under cgi because I have to open too many things up as world writable.
Did the new server setup fix your problems?