High Resource Usage

From Free Hosting Wiki
(Difference between revisions)
Jump to: navigation, search
[quality revision][quality revision]
(+cat)
(Added HRU limits, Wordpress info)
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 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 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.
+
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.
 +
 
 +
As of [http://x10hosting.com/forums/news-announcements/99095-resource-usage-monitoring.html mid 2009], the limits are:
 +
 
 +
* 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. However, Wordpress 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. There currently isn't a way of determining which 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.
 +
# First, note the maximum period that your site runs without getting suspended (e.g. 1 week).
 +
# Disable all the plug-ins but one,
 +
# Then re-enable others (starting with the most important) at twice the suspension period (e.g. fortnightly).
 +
# If your site gets suspended, disable the last enabled extension.
 +
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.
  
 
[[Category:KB]]
 
[[Category:KB]]

Revision as of 02:24, 10 December 2010

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.

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.

As of mid 2009, the limits are:

  • 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. However, Wordpress is a known CPU hog and with just a few plug-ins will cause an HRU suspension. There currently isn't a way of determining which 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.

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