I've been hosting website on a shared hosting providers for a while and recently they introduce a 'CPU throttle' system where the web host will automatically cut down your CPU usage if you 'overuse' the server CPU.
To my surprise, my blog was affected by this new feature and my hosting account is throttled for roughly 30 minutes per day. During this half and hour, my blog will takes 30 - 40 seconds to load (according to my concerned readers) where, in normal time it takes abt than 2 seconds.
I've tried contacting the support and though they are being friendly, they failed to solve my problem. They told me it could be the database error that's causing the problem but there were days when there's no errors and yet my account is being throttled!
1. According to the support, the system will throttle users account when it exceeds 40 CPU seconds in 3 minute - is this acceptable for a $6.95/mo shared hosting package?
2. I am not a computer savvy. When I check my error logs, I see strange error codes like this:
[Sun Oct 04 10:52:12 2009] [error] [client 194.xx.xx.xx] 220-host249.(hostname).com ESMTP Exim 4.69 #1 Sun, 04 Oct 2009 10:52:12 -0600 , referer: http://example.com/blog/?p=16
Can someone tell me what does this mean? What kind of error is this?
3. And also, I see this MySQL error but I couldn't understand. One of the codes:
[01-Oct-2009 20:45:37] WordPress database error MySQL server has gone away for query SELECT t.*, tt.* FROM wp_terms AS t INNER JOIN wp_term_taxonomy AS tt ON tt.term_id = t.term_id INNER JOIN wp_term_relationships AS tr ON tr.term_taxonomy_id = tt.term_taxonomy_id WHERE tt.taxonomy IN ('category') AND tr.object_id IN (17) ORDER BY t.name ASC made by do_action_ref_array, call_user_func_array, GoogleSitemapGeneratorLoader->CallBuildSitemap, GoogleSitemapGenerator->BuildSitemap, get_permalink, get_the_category, wp_get_object_terms
It seems something related to one of my plugins (GoogleSitemapGenerator) but things were working alright previously and I've done no change to the code at all. Any WordPress users (who's using this plugin) having the same problem?
Thanks in advance for whoever that read (and comment) this post. Your help is very much appreciated and I really wish to learn if it's my responsibility for the problem; or it's just that I need a new web host.
Cheers and regards, Tahiti
[edited by: eelixduppy at 6:23 pm (utc) on Oct. 4, 2009]
[edit reason] exemplified [/edit]