And feeling ground down.
Now that I’m on my own server (Brizi) … I’m still getting swacked with various spammy attacks. Bleah. None of the spam is getting through — but it’s trashing the server performance.
Bleah.
So the next step is the upgrade to Movable Type 3.34 which (once my host implements FastCGI on the server) will detect FastCGI once properly configured and run much faster and
(so they say) reduce the impact of all those hits to the various comment/etc. modules.
That’s the theory, at least. Sounds like something entertaining to dabble with on a Friday afternoon …
87 view(s)
I used to have the same problem, and the solution was WordPress. I resisted for a long time, but once David set up a test blog “just to play with” and that’s all it took. Of course, we do our own hosting here, and David runs his own webserver, so he’s got a lot more control over things. But even so, its built-in anti-spam plugins (we use Spam Karma 2) do the job but good.
Biggest problem with MT isn’t that it doesn’t have fine anti-spam plug-ins, both built-in and available from other parties for free — it’s that it’s Perl-based, which (as I undestand such things) means that all sorts of processing overhead gets taken up in order to execute those fine anti-spam bits. Which means that a spam attack might not get through, but it makes sure that nothing else gets through, either.
The FastCGI solution (which I’m now going to attempt — nothing up my sleeve — will ostensibly make things execute much faster as modules will get loaded and stay loaded in memory. Perl will still be inefficient, but it will be much more efficient in its inefficiency.
I will say that there are a lot of folks who have a lot of success with WP, and with some of the other tools out there. And if I weren’t terrified of the effort to convert over, I would be giving that a lot more consideration.
*sigh*
(Test, test, test)
3.34 installed (albeit not very … elegantly). The blog seems to be working, but I can’t seem to get the FastCGI implementation to work. I will poke further with it tomorrow.
(Test, test, test)