My hosting package resources are reaching their limits. What does this mean and what can I do?

If you notice slow website performance or encounter errors such as 502, 503, or 508, one or more of your hosting package resources may have reached their limits.

In Shared Hosting and Semi-Dedicated Hosting environments, resource usage is controlled through CloudLinux and the LVE Manager, ensuring that each hosting account can only use the resources allocated to its package.

Each hosting package includes predefined limits for resources such as CPU, RAM, Disk I/O, and processes. When one of these resources is exhausted, your websites may experience slowdowns or service interruptions.

How Can You Tell If Your Package Resources Are Being Exhausted?

When one or more resources consistently reach their limits, you may notice:

• Slow website loading times.
• Website downtime or intermittent availability issues.
• Errors such as 502 Bad Gateway, 503 Service Unavailable, or 508 Resource Limit Is Reached.
• Delays when accessing your website's administration area.
• Failed cron jobs or other scheduled tasks.

What Are CloudLinux and LVE Manager?

CloudLinux is a Linux-based operating system designed specifically for shared hosting environments. It isolates each hosting account and controls the amount of resources it can consume.

LVE Manager (Lightweight Virtual Environment) is the technology responsible for monitoring and limiting resource usage for each account. This prevents a single website from consuming excessive server resources and helps maintain overall server stability and security.

Which Resources Are Limited and How Do They Affect Your Websites?

CPU (Processing Power): CPU limits determine the maximum processing power available to your hosting package. When the limit is reached: Your websites may become slower as processes are temporarily throttled.

Physical Memory (RAM): This is the maximum amount of memory your hosting package can use. When the limit is reached: You may encounter errors such as 503 Service Unavailable or Internal Server Error.

Input / Output (I/O): I/O limits control the rate at which data can be read from and written to the disk. When the limit is reached: Your websites may experience delays and, in some cases, 502 Bad Gateway errors.

IOPS (Input/Output Operations Per Second): IOPS determines how many read and write operations can be performed simultaneously on the disk. When the limit is reached: You may notice a general decrease in website performance.

Entry Processes (EP): Entry Processes represent the maximum number of simultaneous dynamic connections to PHP applications, CGI scripts, SSH sessions, or cron jobs. When the limit is reached: Errors such as 503 Service Unavailable or 508 Resource Limit Is Reached may occur.

Processes (NPROC): This limit refers to the total number of processes that can be created by your hosting package. When the limit is reached: You may experience delays or encounter 502 and 503 errors.

How Can You Check Your Resource Usage?

You can monitor your package's resource usage through Plesk.

1. Log in to Plesk.
2. From the right-hand menu, select Resource Usage.
3. A report showing resource usage for the last 24 hours will be displayed.
4. Click Details to view detailed resource usage graphs.
5. In the Faults graph, you can see whether any resource limits have been reached and when they occurred.
6. The Usage table provides a detailed hourly breakdown of resource consumption.

What Can You Do If Your Package Resources Are Not Sufficient?

The most common causes of excessive resource consumption include:

• Increased website traffic.
• Aggressive crawlers or bots.
• Problematic plugins, themes, or scripts.
• Cron jobs running too frequently.
• Websites whose requirements exceed the resources available in your hosting package.

1. Identify Which Website Consumes the Most Resources

If you host multiple domains within the same package, determine which website generates the highest number of requests or log entries.

You can use the logs available in Plesk to identify which website has the highest activity level or generates the most errors.

2. Review Your Logs During Peak Usage Periods

Use the Resource Usage graphs to identify when the resource limit was reached and examine the corresponding log entries.

Pay particular attention to:

• IP addresses generating a high volume of requests.
• URLs that appear most frequently.
• Errors recorded in Apache or Nginx logs.
• User Agents generating the requests.

3. Check for Aggressive Crawlers or Bots

If you identify excessive traffic originating from specific IP addresses or networks, an aggressive crawler may be responsible.

In this case, you can:

• Restrict access using the .htaccess file.
• Configure appropriate rules in the robots.txt file.

4. Review Your Cron Jobs

If the excessive resource consumption is related to cron jobs:

• Verify that they run at appropriate intervals.
• Check whether any cron job is taking too long to complete or repeatedly failing.

5. Review Your Website Application or CMS

If you use WordPress, Joomla, or another CMS:

• Keep the CMS, plugins, and themes up to date.
• Remove plugins that are no longer in use.
• Make sure your PHP version is compatible with your application.
• Enable debugging if necessary to identify problematic functionality or requests.

When Should You Upgrade Your Hosting Package?

If you have reviewed your logs, ruled out problematic requests, bots, cron jobs, and configuration issues, and your websites continue to reach resource limits on a regular basis, your hosting requirements may have outgrown your current package.

In this case, upgrading to a hosting package with additional resources is recommended to ensure the smooth and uninterrupted operation of your websites and services.