What are CPU Quota/Suspension Errors?

CPU Quota/Suspensions Errors are used as a maintenance tool to help avoid server lockups by preventing customers from running inefficient scripts that monopolize unnecessary CPU time and slow your server down.

Why do I get CPU Quota/Suspension Errors?

CPU Quota/Suspension Errors are currently triggered by a single process taking more than 30 CPU seconds to run or if your total processes take more than 40 CPU seconds in any 60 second window. They are set up like this to avoid server lockups. Your site will generally come back up after 5-10 minutes of suspension. In some cases the following issues may trigger CPU Quota/Suspension Errors:

• Over sized and unnecessary database queries can lead to performance issues. Optimize your applications to use less CPU by adding appropriate indeces (index) to your MySQL tables.
• Poorly coded .php scripts may lead to extended processing times. Try using static .html documents instead of .php scripts; doing so will practically eliminate CPU Quota Suspension/Errors

How can I prevent more CPU Quota/Suspension Errors? If you receive several CPU Quota/Suspension Errors a day or notice this to be a repetitive issue, we encourage you to consult your personal designer, programmer or webmaster. As these issues are the account holders responsibility to resolve, XwebHosting Technical Support is not authorized to trouble shoot your scripting or database programming issues on your behalf. Please have your designer, programmer or webmaster review your detailed log files by doing the following:

1. Log into your XwebHosting Control Panel.

2. Locate the Files menu.

3. Locate and click on the File Manager icon.

4. When the Directory Selection menu loads select the Home Directory option.

5. This will take you to the Root ( / ) directory of your File Manager.

6. Locate and double click on the tmp folder.

7. Inside this folder there are two folders that may have information pertaining to this issue; the cpu_exceeded_logs and mysql_slow_queries.

8. The cpu_exceeded_logs folder will contain individual log files listed in order by date. If you wish to view the details of these log files right click on the file you would like to open and select View from the drop down list.

Important: The cpu_exceeded_logs contain important information about which processes you were running and their lengths that co-inside with your cpu exceeded errors.

Example:

Fri Jul 7 17:07:36 2006: used 716.27 seconds of cpu time for HTTP Request: yourdomain.com: GET /img_yourproducts/shop_images_026.jpg HTTP/1.1

Fri Jul 7 17:07:37 2006: used 0.18 seconds of cpu time for HTTP Request: yourdomain.com: GET /img_yourproducts/shop_images_027.jpg HTTP/1.1

9. The mysql_slow_queries folder will contain individual log files listed in order by date. If you wish to view the details of these log files right click on the file you would like to open and select View from the drop down list.

Important: The mysql_slow_queries contain important information about which queries you were running and their lengths that co-inside with your mysql_slow_queries errors. These will appear much like the above logs. only providing details on your particular mysql queries.

Example:

Tue Aug 28 11:54:54 2007:
Query_time: 4 Lock_time: 0 Rows_sent: 0 Rows_examined: 0
use yourdoma_yourdoma;
update SS_categories set viewed_times=viewed_times+1 where categoryID='665'

Tue Aug 28 11:54:56 2007
Query_time: 2 Lock_time: 0 Rows_sent: 0 Rows_examined: 0
update SS_products set viewed_times=viewed_times+1 where productID='21925'