High Resource Usage
|[checked revision]||[checked revision]|
|Line 6:||Line 6:|
As of [http://x10hosting.com/forums/news-announcements/99095-resource-usage-monitoring.html mid 2009]
[http://x10hosting.com/forums/news-announcements/99095-resource-usage-monitoring.html mid 2009] :
* 25% CPU utilization
* 25% CPU utilization
Revision as of 12:56, 20 September 2011
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.
How to Unsuspend Yourself
- Open your Account Portal and sign in.
- Click the link in the red bar (see image below).
- Click the button that says "Unsuspend Account" (see image below).
As of fall 2011:
- 300 seconds of CPU time per hour
The previous limits from mid 2009 were:
- 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 (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.
- 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.
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.