Posted 6 years ago #
Greetings all,
Given a 'fresh-out-of-the-box' wordpress install, what is the best method of preparing a site for a potential slashdotting, dugged(?) or farking etc. Further, in wordpress 2.0.1, is wp-cache still useful?
I found a bit of info in the codex, and some in various posts on these forums but I'm not sure how out of date they are given the 'Persistent Cache' of WP 2.0. Assume that no intensive plugins are running.
Any help would greatly appreciated!
Posted 6 years ago #
The default cache is 2.0.1 is meant to relieve the load in such situations though wp-cache may be better ....
This draft document should help explain some of the concerns. The slashdot effect very often crushes your network before it crushes your server. Or your Apache is too busy spawning children that your WordPress configuration never really becomes an issue, because you've exhausted your free memory...
Posted 6 years ago #
Thanks for the link, I've read over that document already and while helpful, there is nothing *I*, as a joe wordpress user, can do about hardware / bandwidth. Specifically, I want to know what I can do on my end to aid the situation? Does wp-cache work in the new wp 2.0 or is it redundant? There is no solid answer at this point.
Posted 6 years ago #
Actually, WP-Cache (or Staticize) has ALWAYS been THE answer for potential high-load scenarios -- and still is.
The new WP2 object caching mechanism has somewhat minimal impact on overall performance. Maybe under extremely high loads it'd help some, but nothing of the magnitude of WP-Cache.
Also, I agree with skippy at some level... the server can get submarined without even really hitting the site. It's like a Ddos attack almost. However, it's been shown that replacing Apache with something like lighttpd can make a huge difference in server load (memory, cpu, etc.) under a slashdot/blowout.
-d
Posted 6 years ago #
Thanks for your reply and input. Sorry for the delay in thanks... I really appreciate your thoughts.
Posted 6 years ago #
Try this WordPress plugin, which redirects Digg et al to a Coral Cache server.
Posted 6 years ago #
Right. If your network resources, or Apache, croaks because of the basic overhead, any redirect or static system won't help. If you pass the resource issues, they do.
Another approach would be a plugin that tracks and detects heavy volume access to a given article, and then 'rewrites' the page in a low-bandwidth method. The low-bandwidth page could even then get WP-Cache'd, for super savings... I'll think about this for an updated CG-Referrer version -- maybe use it to do the detection, then set a flag that another plugin could use to load up a different template file or some such thing...
-d
This topic has been closed to new replies.
