Persistent Spam floods have taken over again. I wish these people would quit since it is not only hurting my blog, it is also hurting their own purposes. If spammers realize that if they flood/kill their victims, they do not get the spam on the blog. It is a lose-lose situation. In addition to spam floods, Performancing has been having some serious problems with their servers (I read something about a server move) and that has been causing slowdowns and random problems. I have disabled both for the time being. I have a message in to Chris about the ad problems and I hope to hear back soon but the ads will stay off until things settle down. As for comments, they will remain turned off until the spammers decide to move on.
There HAS to be a solution to stop comment floods. For those that have suggested Bad Behavior in the past, I would like to report that it also fails in stopping the flood. As a matter of fact, it added to the http load and spawned off enough processes that Apache reached its set limit. At this time, the comment post script has been removed to reduce some of the load. As you can see from the processor graph for this particular server, it has been taking quite a beating from all of this.
I would like to say that I have the inclination to come up with a clever script to automagically rename the comment post script when a flood starts, but sadly I doubt I will have the time.
[EDIT] Comments are back on. No word from Performancing.
[EDIT] Received a second email from Chris from Performancing and it has been restored.