News for hackers. Stuff that matters.
Re:Bring down a poorly deployed WordPress (and how to stop i... by jalada on Saturday February 05, 2011 @11:00AM (#2183277)
True, and true. The main issue with caching WordPress is that WordPress itself is very dynamic and full of cookies, WordPress has plenty of caching plugins available but as I point out, that wont help you against Apache spawning tens of processes and eating all your RAM.

So therefore you're down to external caching, which is another layer of complexity and detrimental to anything dynamic you have on your blog (which is pretty common).

Re:Bring down a poorly deployed WordPress (and how to stop i... by sabat on Monday February 07, 2011 @10:50AM (#2189326)
You're right, it caching won't help directly. But if every hit takes a tiny fraction of a second because it's (at least mostly) cached, it will take a lot more to overwhelm Apache. Caching Wordpress is not trivial, but it's not necessarily all that difficult -- it depends on the particular blog and how dynamic it has to be. I've had success setting up caching for my own stuff as well as a high-traffic online magazine.

Your larger point, BTW, that Apache can be overwhelmed, and that it makes a lot of sense to do some math and tune the configuration -- makes a lot of sense. I'd not really thought about that in depth before, but it seems obvious now. :-)