LiquidWeb just acts like Communitech :

They did close my account because I was using too much of the CPU.
Even if I didn't exceed the 30 Gb bandwidth. Nice...

They suggested me to look into a dedicated server (250$... per month plus setup fee).

Communitech at least warns you a few hours before closing your account but LiquidWeb didn't warn me. Nothing at all.

Stay away from this fu***ng company.

What happened to your website if they just closed your account? Was the site backed up by you?

CPU resources and Bandwith are two different things.
Maybe you should've asked if you can run CPU intensive scripts before doing it? Just a thought.

BTW Same thing happened to me, and keeping in mind they are shared hosting I couldn't really argue with them since I was sharing that PC with 100+ or - other people.

So in all fairness I think it was a good move for them to terminate your account to make it so the other 99 customers don't complain because one account takes up too many of their resources.

good luck and I hope you find a host that suites your needs.

It would have been nice if they had given a little warning first, though. Or backed up his site. Or asked that the CPU-intensive scripts be taken down or deleted. Not everyone backs up their site. (Even though you should.)

What were you running?

I'm right now writing a new PHP site and use quite a lot of nested include files (using PHP include directive) wonder if that will cause much CPU usage.

I have no experience with it, since the site isn't open for public yet...

Originally posted by astra4
What were you running?

I'm right now writing a new PHP site and use quite a lot of nested include files (using PHP include directive) wonder if that will cause much CPU usage.
From what I've read, PHP4--run as a module and not a CGI--is significantly less resource intensive than Perl. A PHP include() is probably one of the least resource-using things you can do with PHP, so you should be okay, regardless of how complex your include() pages are.

Anything run as a module uses less resources than the alternative, that's why all hosts who support perl should be running mod_perl.

Was wondering recently how many gigs data transfer you use?

What I believe whether your site using a lot of CPU resources or not, once your site take a lot of bandwith they will close your account simply by saying that your account take a lot of CPU resources.

Because that's the "simple and powerfull reason" to kick you.

I was using 1 gig per day approximatevely.
And my site uses PHP/mySql with 2500-3000 hits per day.

It happened a few weeks ago and it took me a week (without my site being accessible during this time) and several eMail to the support to have access to my site again (by FTP).

-- eMail from Ross (support):

Your site has been deactivated due to content that crippled our servers. Your bandwidth was going at a rate that would have exceeded the maximun allowed value in a month. Our suggestion would be to look into a dedicated server.
--

1) Actually I didn't exceed the maximum transfer allowed (30 gigs per month).
2) They thought I would use their dedicated server plan and give them 250$ per month instead of 24.95$...
3) And they could have at least warned me a few hours before doing this.