If you see this website not responding from time to time, it’s because it’s currently being targeted by a network of spambots that try to post with such violence that they manage to bring the system to its knees.
The problem is not so much identifying spam—Akismet does that perfectly well 99.99% of the time. The problem is that, precisely because of Akismet, each post will tie up an Apache child process for a significant interval of time and those bots are posting so quickly that they will make the server reach the configured limit on the number of server processes in a matter of seconds.
I could raise that number, but this system hasn’t got a whole lot of memory, and I would hate shelling out more money just to keep those bots at bay. Barring a reconfiguration of Apache to use a different multiprocessing model or anything that would cost me a significant amount of time—after all, one of the reasons for using WordPress on Apache is just because it simply works, most of the time, and requires very little maintenance— one option left to me is harvesting the IP addresses of those bots and block them using iptables.
Of course, it’s an uphill battle, and I’m afraid I will quickly reach a point where the kernel will start sweating just to check every packed against a huge list of source addresses (I have more than 700 right now in this file, which you are free to reuse if you have the same problem). Probably most of those PCs (fuck Microsoft and its idea of security, by the way) have dynamic IP addresses, which just makes the problem bigger.
Anyway, this strategy seems to be working for now, so I’ll stick to it. If you’re curious, all the bots in this recent wave exhibit the following User-Agent string:
Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; Maxthon)