A site uses over and above its limit of server resources for a number of reasons. However, it is not always followed by a major change in your website as it is not expected often, which makes it very difficult to find the issue and resolve it conclusively. These resources would help you in this issue resolution.
In order to troubleshoot the issue of resource over usage, you need to know and understand the limit of your account resources and what would happen when that limit is reached.
Summary of Account Limits
When a site is hosted with ZNetLive, there are some restrictions on the users depending upon the resource availability on their individual servers irrespective of the server or site size. This article sums up these limitations.
CPU Resource Usage
CPU Resource Usage
CPU usage may be defined as the amount of processes and tasks that simultaneously run on a computer at any given time. All ZNetLive servers are bound by this restriction. Following write-up would give an overview on this.
ZNetLive regularly tracks all CPU usage on Reseller, Shared and VPS plans. The limitation on CPU resource usage for each hosting option is given in detail below.
A maximum CPU Usage limit of 5% is permitted by ZNetLive. Resource restrictions are imposed on the account if upto 25% CPU resources are utilized for 5 seconds.
However, your possibility of hitting limitation of 5% CPU usage is unlikely unless there are intensive scripts on your site that require detailed processing.
CPU usage can be reduced by following certain tricks given below:
Ads and banners from other sites should be reduced.
Usage of too many scripts should be avoided and html should not be forced for handling server-side code (like shtml and php).
Usage of https protocol should be avoided as encrypting and decrypting communications is much more CPU-intensive than unencrypted communications.
Note: Audio, video, image and Flash only use bandwidth and not CPU, as they are downloaded to the browser.
The limit on reseller servers is same as that of shared servers; however, the limit is not for entire reseller package but as per cPanel.
If you have multiple cPanel accounts that are contributing to a server problem, any of them may be suspended.
In VPS, you can use complete 100% of your CPU resources. However, this 100% is only a part of the total CPU resources of the server. In case you intend to use more CPU resources than a shared server, then instead of VPS, you should go for a Dedicated Server.
In dedicated servers, you can use 100% CPU resources of the server.
In case of VPS and dedicated servers, you can decrease your CPU usage by turning off the webstat programs (AWstat) that comes with your cPanel, as different tracking tools like AWstat utilize MySQL and CPU connections.
- Is there any limitation on concurrent processes?
The limitations on concurrent processes depend upon the type of hosting account you are having.
Shared and Reseller
A limitation of 25 simultaneous processes per every cPanel is enforced for shared and reseller accounts. 25 concurrent processes are sufficient for most sites to work perfectly well and processes close and open quickly so that overlapping is quite uncommon.
VPS and Dedicated Servers
VPS and Dedicated Server hosting plans permit a flexible number of simultaneous processes without any enforced limit as such.
- How can I check processes in cPanel?
You can follow the steps given below to check the processes in cPanel:
Log into cPanel.
Scroll down to reach the Statistics section.
Search for the Processes bar and you can check the number of simultaneously running processes at a time.
The bar normally refreshes in a minute; however, you can refresh the page before that, if you intend to see the updated processes sooner.
Important: These instructions are not for Reseller account holders. Please contact us in case you hold a reseller account and require viewing of the number of running processes.
- How to find out if the mail client is creating the problem?
If a website is surpassing the processes limit because of the mail client, then following steps can be tried for determining it:
Clear all processes by closing the mail client. You will see that your site will load back immediately.
Once the site is up and running, open the mail client and search the setting for the number of times the mail client is checking the server for mails. This setting should strictly be over 10 minutes apart.
If after following all these steps you still reach the process limit, then you would require optimization of your database for faster queries or if you are having more traffic than a shared server can handle. Please create a ticket or contact us through phone or live chat so that the issue can be assessed properly.
- How can my inode count be reduced?
In order to reduce the inode count, simply delete any emails, files or images that are no longer needed.
- How to view the number of inodes that I am using?
Dedicated & VPS customers through SSH can check an account’s inodes on their server:
You can utilize the following command to see the inodes of a particular folder via SSH access:
echo "Detailed Inode usage for: $(pwd)" ; for d in `find -maxdepth 1 -type d |cut -d\/ -f2 |grep -xv . |sort`; do c=$(find $d |wc -l) ; printf "$c\t\t- $d\n" ; done ; printf "Total: \t\t$(find $(pwd) | wc -l)\n"
This command provides a clean detailed and formatted inode usage list on your account.
TOS Inode violations can consist of a number of reasons, including but not limited to:
Continuous deleting and publishing a large number of files, over 10,000+
cPanel account exceeding a limit of 250,000 inodes etc.
Reseller and Shared Accounts
A soft limit of 100,000 files for each cPanel is there and accounts surpassing more than 250,000 files will be susceptible to suspension, as they are in direct violation of the terms of service.
A limitation of one million inodes has been set for the VPS customers. However, this limit can be raised for any valid reason.