I’d imagine the problem is Wordfence causes additional load due to evaluating all incoming traffic, and you have a wimpy server, saying “Wordfence causes” might be over-stating the case. Fact is, if you have the traffic you need the server to handle it, otherwise you’ll spend hours, days, months struggling with stuff that “causes.”
If your server crashes due to too much traffic, and it’s real traffic, that’s a good thing. Get it handled and enjoy.
And beware, once you have a website with “real” traffic prepare to enjoy the bot swarm.
MTN
It’s not really a wimpy server, it has 1GB RAM — and I’ve never experienced this before. I can’t find anything on the logs regarding the crawlers or hits – so can’t even be sure it’s that
Are you on a dedicated server or shared host? It could be a processor issue.
-Brian
it’s a dedicated VPS
it’s like it can’t handle the GET or HEAD requests from twitter crawlers and crashes the DB – that would be my guess. But it’s weird.
Wow, that really is kinda weird. When you figure it out please share. Still could be a server configuration issue. Perhaps do a load test you have total control of.
1 GB RAM! Nice.
MTN
