Update on the DWHS Hosting Debacle
 

So 10 hours later I get an email telling me that my "cron jobs" were overloading the server so they temporarily suspended my sites.
Cron jobs in this case being a wp tube site which was stagger/auto updating feeds 24 times a day, so i cut that in half to 12 times a day, and if that doesnt work i will move the sites to another server. Keep in mind i have 9 normal blogs on the server and the one wp tube for a total of less than 10k traffic per day right now as they are very new.

The bottom line is when there is a problem with server overload shouldn't the hosting company at least email the client to say "we are suspending your sites because you are overloading the server"

Seems reasonable to me.:helpme

dude, get off that host, no one uses them.

you're probably right, hate to chuck a years paid hosting out the window though.
i'm keeping non-essential blogs on there for now so if it happens again the impact will be minimal.

Did you consider optimizing your cron scripts?

Why should they wait for you when you're disrupting service for their customers? What if you sent an email to your host because their server was slow, and they told you "We are waiting for our other customer to respond because his website is using too many resources."

Upgrade to a dedicated server if you don't want to have to worry resource usage.

you are ultimately correct, but what i said was they should at least have sent an email saying they were suspending my sites because of overload. thats it, i could have gotten an email and taken care of the problem on the spot as opposed to 12 hours later. so my site may have been down for an hour as opposed to 10.

i understand the drawbacks of virtual hosting, but sending an email notification of suspension should be a basic thing for any hosting company.

A lot of hosts are ran like this. Over time you see some shady stuff or at least blatant disregard for the customer. My favorite used to be calling and always being told that "All techs are in a meeting". Another I caught throttling each thread down to 50K ( 400 kb/s) without disclosing it. 50K just doesn't work well for streaming video and it isn't acceptable when you are paying for 100mbit DEDICATED bandwidth and not even utilizing half of that while this is going on. :helpme

Any competent admin would merely disable the offending cron jobs or disable the ability of the user to schedule cron jobs until it is cleared up. Suspending the websites is a little ridiculous and not necessary.

I've noticed that sometimes reps will use stuff like this to try to "shake you down" and get you to upgrade. I remember one trying to tell me that the reason my sites were slow (on a shared host) is that I needed to upgrade to their premium offering since I had more traffic than before. But the reality was that I had 80% of the traffic I normally had due to the sites being slow. He was only trying to get me to pay more.

Happened to me years back when I was starting out with my forum on another shared hoster.
They just deactivated the index file and therefore killed the site.

Nowadays, the host keeps tabs of the memory usage and just shows internal server errors if you use all your allowed memory.

Are you on a virtual/shared/vps or dedicated server setup?

DWHS is the shittiest host I've ever had and the best thing I ever did was leave them

q f t