Resource Limits – Detailed Information

Sometimes, the server resources available in the purchased hosting package may prove insufficient for the applications running on the hosting account. This can result in the website displaying errors to customers (error 500 or error 508). Displaying errors, especially for an online store, can interrupt transactions or payment processes, while for regular websites, display errors can cause reputational damage.

How to detect resource overages?

To meet customer expectations, notifications are sent every 14 days to customers whose hosting account resources have been exceeded. The message includes information on which resources were exceeded and the number of occurrences. A sample message is shown below.

You can also independently verify if resources have been exceeded in cPanel by clicking on Resource Usage.

What these parameters means?

CPU resources – This is the number of processor cores available within the purchased package, responsible for the computational power needed to perform tasks on the hosting account.

RAM resources – This is the cache memory used to temporarily store data during operations.

EP resources – This is the number of simultaneous HTTP processes (i.e., processes handling HTTP requests, such as Apache, LiteSpeed, or other web server processes).

Number of processes resources – This is the number of processes that can run simultaneously within the account. Processes are programs or tasks running on the server, such as PHP scripts, web applications, databases, webmail, etc.

I/O operations resources – These are processes related to data transfer.

How to verify which process is causing resource overages?

To verify the process causing the resource overages, go to the panel by clicking on Resource Usage and then Snapshots.

In the Snapshots tab, you can check various dates when the resource overages occurred.

What to do if resources are being exceeded?

If resources are being exceeded, it is best to first contact the website developer for optimization, so that loading the website/store uses fewer resources on the hosting account.

Additionally, analyzing server logs can help in understanding resource usage by the application. All logs are available in the logs directory on the hosting account. Each domain will have its own directory, for example: account_name.smarthost.eu-Oct-2023.gz (for HTTP access) and account_name.smarthost.eu-ssl_log-Oct-2023.gz (for HTTPS access).

Konrad

Leave a Reply