Under Shared Hosting plans, resource limits are set by CloudLinux LVE (Lightweight Virtual Environment).
Depending on your style, you may see the below resources either on your left or right panel.
(To view the resources for your hosting plans, kindly log into your cPanel (https://domainname.com/cpanel)
Resource available for checking:
Physical Memory Usage
Number of Processes
CPU Usage : 100%
CPU Usage is one of the indicator for speed of loading for website.
Hitting CPU Usage 100% will cause your site to slow down until CPU Usage is below 100%.
No error will be displayed for hitting CPU Usage limit.
Physical Memory Usage : Based on package
Physical Memory depends on the package you subscribed.
“508 Resource Limit Reached” or “500 Internal Server Error” may be displayed for hitting Physical Memory Usage limit.
Entry Processes : 20
Entry Processes is the number of concurrent Apache connections a website can sustain.
The word 'concurrent' refers to processes happening at the same time.
You could have hundreds and thousands of connections but having all connections performing tasks simultaneously is unlikely.
Hitting this limit generally hints that the site is getting hit hard by bots and crawlers.
“503 Service Temporarily Unavailable” will be displayed for hitting Entry Processes.
Number of Processes : 100
Number of Processes refers to total number of active processes allowed on a domain.
Services below are examples of the processes:
HTTPD (website connections)
Hitting this limit will require one process to end for the next one to be generated.
Apache 500 or 503 errors will be displayed for hitting Number of Processes limit.
IOPS : 1024
IOPS refers to Input/Output per second. This resource limits the total number of read or write operations per second.
This limit does not usually get hit as other resource will be hit before IOPS is hit. If it does hit, it will be queued for the next operation after the current one ends.
One of the indicator is slow loading of web pages.
I/O Usage : Based on package
I/O Usage refers to Input and Output. I/O Usage refers to the work done by drives to read and write data.
Hitting this limit will cause website to slow down (but still available) until the usage has decreased.
Domain names hosted in the same account shares the same resources. Thus, other domain names in the same account will be affected if one of the domain has reached its limits.
Steps to check and resolve resource overusage
Step 1 : Check usage and limit
Login credentials has been sent out together with the Welcome email. If you didn't receive the Welcome email, may kindly submit a case to our support and request for reset of login credentials.
Please do take note that the case submission must be done via primary email.
In order to ensure resource usage does not hit the limit, it is important that monitoring is done regularly for early prevention methods.
Step 2 : Fix excessive resource usage
Even though the above error is displayed, you may access cPanel with the servername link https://servername:2083 to disable or modify scripts that cause overuse.
Step 3 : Errors (500, 503 and 508)
Issues delayed a few minutes
Please check the running processes or contact our support for further assistance.
Issues delayed a few seconds
Please check the resource usage in cPanel by clicking on CPU and Concurrent Connection Usage via cPanel. You may just find out the resources that has reached its limits.
Step 4 : Troubleshooting Section
- Recent site updates
- Check the latest updates that may impact usage levels.
- New plugins/themes
- Changes will not take effect immediately. Do allow 1 to 2 hour before accessing page again.
- Increase of site traffic
- Go to Awstats in cPanel for monitoring of visits. Review of current plan may be done with customer service team for upgrade of plan.
- Website Optimization
- May utilize tools such as Google Page Speed, GTmetrix and Pingdom.
Checking Process via SSH / commands
Command top -c
This command allows you to check the process that consumes your resources.
It identifies the number of tasks and whether these are running, sleeping or have stopped.
If the process is generated by a script, the simplest way to disable use of this script is to rename it. OR
you can create a Deny from all record in the .htaccess file where the problem script resides.