High Resource Usage

From Free Hosting Wiki
(Difference between revisions)
Jump to: navigation, search
[checked revision][checked revision]
(Resource Limits)
(update per new HRU policy)
Line 1: Line 1:
To prevent abuse to the free hosting servers, x10 has implemented a policy where it suspends accounts that reach and bust the limit placed on server resource usage. This means that resource intensive scripts can possibly get flagged by the system, even if it's the only time they will be ever ran.
+
To prevent abuse to the free hosting servers, x10 has implemented a policy where it temporarily suspends accounts that reach and bust the limit placed on server resource usage. This means that resource intensive scripts can possibly get flagged by the system, even if it's the only time they will be ever ran.
  
High Resource Usage (HRU) is a minor suspension as too you can unsuspend yourself for the first 2 times. After that, you will have to create a ticket and have a [[Community Support Representative]] unsuspend you.
+
The type of suspension issued by High Resource Usage (HRU) is different from other suspensions in that in only blocks access to your website. You can still log into cPanel and FTP to attempt to fix your issue. Any account found breaking the resource usage limits will be suspended for 1 hour. [[Community Assistant]]s are unable to unsuspend you for HRU suspensions, you must wait the hour.
 
+
{{Template:UnsuspendYourself}}
+
  
 
==Resource Limits==
 
==Resource Limits==
 
As of [http://x10hosting.com/forums/free-hosting/168812-sql-error-mysqli.html fall 2011]:
 
As of [http://x10hosting.com/forums/free-hosting/168812-sql-error-mysqli.html fall 2011]:
 
 
* 300 seconds of CPU time per hour
 
* 300 seconds of CPU time per hour
  
The previous limits from [http://x10hosting.com/forums/news-announcements/99095-resource-usage-monitoring.html mid 2009] were:
+
To get your suspended, your site has to surpass the above limit. Usually, reaching that limit indicates a bug in your scripts.  
 
+
* 25% CPU utilization
+
* 5% of memory
+
* 240 seconds of CPU time per hour
+
* 20 concurrent processes executing
+
 
+
To get suspended, your site has to surpass only one of those limits. Usually, reaching any of those limits indicates a bug.  
+
  
 
===Wordpress===
 
===Wordpress===
 
 
Wordpress (WP) is a [http://www.codinghorror.com/blog/2008/04/behold-wordpress-destroyer-of-cpus.html known CPU hog] and with just a few plug-ins will cause an HRU suspension. A caching plug-in should help reduce WP's load on the server, but it may not be sufficient to prevent HRU suspensions, and on large sites will actually cause high resource usage during the cache generation.   
 
Wordpress (WP) is a [http://www.codinghorror.com/blog/2008/04/behold-wordpress-destroyer-of-cpus.html known CPU hog] and with just a few plug-ins will cause an HRU suspension. A caching plug-in should help reduce WP's load on the server, but it may not be sufficient to prevent HRU suspensions, and on large sites will actually cause high resource usage during the cache generation.   
  
Line 30: Line 19:
 
You can try to reduce the test period by running a load test on your site. Basically, find out your site's peak usage and use some tool to request pages on your site at double the peak frequency. If this doesn't cause an HRU, you can enable more plug-ins and repeat the load test. However, this run the risk of being identified as a [http://www.us-cert.gov/cas/tips/ST04-015.html denial of service] (DoS) attack and getting your IP blocked by the [http://en.wikipedia.org/wiki/Firewall_(computing) firewall].
 
You can try to reduce the test period by running a load test on your site. Basically, find out your site's peak usage and use some tool to request pages on your site at double the peak frequency. If this doesn't cause an HRU, you can enable more plug-ins and repeat the load test. However, this run the risk of being identified as a [http://www.us-cert.gov/cas/tips/ST04-015.html denial of service] (DoS) attack and getting your IP blocked by the [http://en.wikipedia.org/wiki/Firewall_(computing) firewall].
  
If you re-enable extensions more frequently, you can't be very sure that the last enabled extension is the most problematic and is thus the one to disable. Even with a long period between re-enabling extensions, your site still might get the occasional HRU suspension. If all else fails, you could try installing different blogging software. Check [[Softaculous]] or [[Fantastico]] in your site's [[CPanel|cPanel]] for easy installation.
+
If you re-enable extensions more frequently, you can't be very sure that the last enabled extension is the most problematic and is thus the one to disable. Even with a long period between re-enabling extensions, your site still might get the occasional HRU suspension. If all else fails, you could try installing different blogging software. Check [[Softaculous]] or [[Fantastico]] in your site's [[cPanel]] for easy installation.
  
 
[[Category:KB]]
 
[[Category:KB]]

Revision as of 17:40, 10 October 2011

To prevent abuse to the free hosting servers, x10 has implemented a policy where it temporarily suspends accounts that reach and bust the limit placed on server resource usage. This means that resource intensive scripts can possibly get flagged by the system, even if it's the only time they will be ever ran.

The type of suspension issued by High Resource Usage (HRU) is different from other suspensions in that in only blocks access to your website. You can still log into cPanel and FTP to attempt to fix your issue. Any account found breaking the resource usage limits will be suspended for 1 hour. Community Assistants are unable to unsuspend you for HRU suspensions, you must wait the hour.

Resource Limits

As of fall 2011:

  • 300 seconds of CPU time per hour

To get your suspended, your site has to surpass the above limit. Usually, reaching that limit indicates a bug in your scripts.

Wordpress

Wordpress (WP) is a known CPU hog and with just a few plug-ins will cause an HRU suspension. A caching plug-in should help reduce WP's load on the server, but it may not be sufficient to prevent HRU suspensions, and on large sites will actually cause high resource usage during the cache generation.

There currently isn't a way of determining which WP plug-in(s) may have caused a suspension. If this happens to you more than once, you'll have to use trial and error to figure out which plug-ins you can run.

  1. First, note the maximum period that your site runs without getting suspended (e.g. 1 week).
  2. Disable all the plug-ins but one,
  3. Then re-enable others (starting with the most important) at twice the suspension period (e.g. fortnightly).
  4. If your site gets suspended, disable the last enabled extension.

You can try to reduce the test period by running a load test on your site. Basically, find out your site's peak usage and use some tool to request pages on your site at double the peak frequency. If this doesn't cause an HRU, you can enable more plug-ins and repeat the load test. However, this run the risk of being identified as a denial of service (DoS) attack and getting your IP blocked by the firewall.

If you re-enable extensions more frequently, you can't be very sure that the last enabled extension is the most problematic and is thus the one to disable. Even with a long period between re-enabling extensions, your site still might get the occasional HRU suspension. If all else fails, you could try installing different blogging software. Check Softaculous or Fantastico in your site's cPanel for easy installation.

Personal tools
Namespaces

Variants
Actions