An account may receive the “Resource Limit Is Reached” error when it exceeds the resources assigned to it – CPU usage, RAM usage, or concurrent processes (EP) in the hosting account.

Users can investigate the reason why their accounts are hitting their limits using snapshots. Each incident generates several snapshots. An incident occurs when limit faults are generated in a short time period.

To access Snapshots perform the following steps.

Go to your hosting panel cPanel/Plesk, and select CPU and Concurrent Connection Usage:

Click the Snapshots option > Select a date > Select an appropriate Snapshot in the combo box:

Here you can see the processes that were running at the time of the incident and can now begin to debug the issue.

In this example, the process was: lsphp:/home/username/public_html/cloner.php

There are also several common causes that can be involved:

• Normal traffic. – If your site experiences high peaks of normal traffic it can exceed its allocated resources. If this is a regular occurrence we would recommend considering an upgrade to a Virtual Private Server, where no such limits are in place.
• Problems in code. – If there are pages on your site that have speed issues that have been introduced during development, a relatively small number of concurrent page requests can push the site over its resource limits.
• Backend operations. – demanding backend operations such as imports and exports can create a significant load, which in addition to normal traffic can cause resource limits to be exceeded.
• Web Crawlers. – making a high number of requests per second. You can adjust the rate at which e.g. Google requests pages in Google Webmaster Tools.

Get in touch with us if you need more help and we will investigate the issue for you.