Understand Hosting Resource Limits: What is LVE?

All hosting accounts on WebManager.NG’s shared, business, and reseller platforms have resource limits in place. These resource limits are designed to safeguard your account.

What is Resource Limits/LVE

Resource limits refer to predefined thresholds or caps set by a hosting provider or server configuration to allocate and manage the number of resources that an account or website can consume. 

In the past, other users on the server could consume all of the available resources (CPU/Processor, RAM/Memory, or Disk Access) and cause a slowdown for other websites hosted on the same server.

WebManager.NG uses the CloudLinux operating system that has resource limits set by an LVE system, (a Lightweight Virtual Environment). Isolated virtual environments for each user, ensuring that their allocated resources, such as CPU, memory, I/O, and network bandwidth, are segregated and protected to ensure no single user uses up another person’s resources.

WebManager.NG provides ample resource limits that surpass those offered by other hosting companies, granting websites abundant room for expansion. Our ability to offer higher limits can be attributed to two primary factors:

  • We use faster, more powerful servers. A typical server uses the latest Intel Xeon E5 processors, up to 128GB of DDR3 RAM, and fast hard disks with SSD technology.
  • We place fewer accounts per server than our competitors. ‘Overcrowding’ of servers is a common technique used by competitors to try and squeeze more money from customers. WebManager.NG loads our servers with fewer accounts to deliver a better quality of service.

Any shared/reseller account hosted with WebManager.NG may use no more resources than outlined below:

WP Hosting Resource Table

Resource Type WP Kick WP Lexus WP Classic
CPU Limit, %  50  50  100
IO, MB/s  10  10  10
IOPS  1024  1024  1024
maxEntryProc limit, N  20  20  30
Nproc  100  100  100
Physical Memory Limit, GB  1  1  1

Shared /Email Hosting Resource Table

Resource Type Flex Plan Flex Pro Flex Bus Email Hosting
CPU Limit, % 100   100 100  50
IO, MB/s 20 20  20  10
IOPS 1024  1024 1024  1024
maxEntryProc limit, N 30   40 40  20
Nproc 200   200 200  100
Physical Memory Limit, GB  2 2  1


Reseller Hosting Resource Table

Resource Type  Starter Reseller   Pro Reseller   Elite Reseller   King Reseller 
CPU Limit, % 600 1200 1800 3000
IO, MB/s 1500  2500 3500 4500
IOPS 1024  1024 1024 1024
maxEntryProc limit, N 60  120 180 240
Nproc 500  1500 2000 2500
Physical Memory Limit, GB  6 9 12


Should you find yourself reaching the limits of your current hosting account, fret not! We offer a seamless solution. By upgrading to a higher resource package, specifically designed for busier websites, you can enjoy an enhanced hosting experience. Our team is readily available to assist you in this process. Simply contact us, and we’ll be more than happy to help.

How to Check Your Current Resource Usage

You can easily monitor your current resource usage by accessing your cPanel account. Simply log in to your hosting panel and locate the Stats widget on the left-hand side. From there, you can conveniently view and track your resource usage as seen in the image below:

Resource Usage Stat

Understand the Terms Used

CPU Usage

This specifies how much of the allocated CPU resources you are currently using. The amount of CPU resources we provide to each account is the percentage of the server’s resources.

If the CPU reaches 100% it means that your account is using all of the CPU resources allocated, and any new processes will be put to sleep until existing processes are complete. This can cause your website to slow down dramatically and in extreme cases even time out.

Virtual Memory Usage

This corresponds to the amount of memory, processes can allocate within LVE. When the process tries to allocate memory, CloudLinux checks if the new total virtual memory used by all processes in LVE is within the limit set. If it is not, CloudLinux will prevent memory from being allocated, and in most cases this causes the process to fail.

Physical Memory Usage (RAM)

This is the actual memory allocated for your account. Virtual memory is usually a file on a disk drive that the operating system uses to store information (swap-to-from) when the real memory becomes full, for instance, the page (swap) file on a Linux system. Therefore, if you try to publish a big post, it might take all physical memory to do so, but after some time it will be normalized.

If this value reaches the limit you may begin to experience PHP errors (if applicable) on your website, or in very extreme cases may see a CloudLinux error page. These errors are typically only brief and once the user has reduced to below the limit, will automatically clear.

Entry Processes

This is the number of processes that enter your account. It is also known as “Apache concurrent connections”. This value defines how many PHP or CGI scripts you can run at a single time. For example, every PHP page that is accessed by a user will usually generate a single entry process. Many people misinterpret this value as the “number of visitors you can have on your website at once”. Whilst it is true that each visitor accessing a PHP page will spawn an entry process, these processes usually end so quickly that it is extremely unlikely that 10 will be spawned concurrently and at a single moment unless you had a significantly large number of simultaneous visitors on your website at once.

Number of Processes

This is the limit similar to the above but includes all processes generated by the account rather than the specific PHP, SSH, or cron jobs. This number is typically very low, even under high activity, as non-PHP tasks execute and complete even more quickly.

I/O Usage (input/output)

This represents how much I/O (or disk activity) your account is using. Any task which makes use of the server’s disk drive (such as reading or writing to the server) will consume I/O. We limit the maximum disk speed of each account to ensure that no single account can saturate the disk drives which will reduce performance for everyone.

Reaching this limit will cause all processes to slow down (to within this limit) and take much longer to complete. Typically you won’t notice this setting ever increase unless you perform something disk intensive like generating a large backup of your account.

Reasons for ‘Resource Limit is Reached’ Errors

When your website is hitting one or more of its hosting account resource limits, it can result in ‘Resource Limit Reached’ errors or slow down the website. What error will appear depends on the resource limit the account is hitting.

The error 508 appears when entry processes hit the limit. If this limit is reached, mod_hostinglimits will not be able to place the Apache process into LVE and will return error code 508. This way a very heavy site starts returning 508 errors without affecting other users on the server.

However, if the site is limited by CPU or IO – the site will start responding slower.

If the site is limited by memory or a number of process limits – the user will see 500 or 503 errors that the server cannot execute the script.

Everything you do on your website, from uploading files, and installing plugins to having visitors, use server resources. There are factors that could cause resource overuse and we have listed the most common ones below.

Most Common Causes

  • increased legitimate website traffic: your website may suddenly receive a high amount of visitors and the error will be shown until the number of visitors is reduced or the resource limits are increased;
  • backend scripts or cron jobs: scripts running in the background, including automatic backups and demanding cron jobs can create a significant load, which in addition to normal traffic can affect the website performance and cause over usage;
  • web crawlers or search engines indexing your website too often;
  • badly written scripts: scripts and plugins that are outdated or incorrectly coded can malfunction and cause loops. Even a few concurrent requests to such scripts can push the website over its resource limits;
  • DDOS: Denial of service attack overloads the server, making it unavailable for normal use.

You can check the resource usage of your account in more detail following this guide:

How to Check Your Resource Usage

To check the resource usage in cPanel, follow these steps:

  1. Log in to your cPanel account using your credentials.
  2. Once logged in, you will be on the cPanel dashboard.
  3. Look for the “Metrics” section. It is usually located toward the bottom of the cPanel interface.
  4. Within the “Metrics” section, click on the “Resource Usage” icon or link. It may also be labeled as “Server Status” or “Resource Usage Overview.”
  5. You will be directed to the Resource Usage page, which provides an overview of your account’s resource consumption.
  6. On this page, you will find information about CPU usage, memory usage, entry processes, I/O usage, and other relevant metrics.
  7. Take a close look at the resource usage data to identify any potential over usage or issues.
  8. For more detailed information, look for an option such as “Detailed Resource Usage” or “Full Report.” Click on it to access a comprehensive report on your account’s resource usage.
  9. The detailed report may provide additional insights, including specific processes or scripts that might be consuming excessive resources.
  10. Analyze the data and identify any resource-intensive activities or scripts that could be causing the issue.
  11. Based on the findings, you can take appropriate actions to optimize your website’s resource usage. This may involve optimizing scripts, reducing unnecessary plugins, or upgrading to a higher resource plan if needed.

NOTE: If your resource usage limits are being frequently hit, you will see a corresponding warning message on the top of the page with a reference to the exact limits.

Choose the desired period in the Timeframe drop-down and click SubmitQuery:

Monitoring your resource limit/LVE

You will see diagrams and tables showing detailed statistics:

Resource Limits monitoring
Resource Limits monitoring
  • CPU – CPU limits
  • vMEM/vM – Virtual Memory limits
  • pMEM/pM – Physical Memory limits
  • EP – Entry Processes
  • nPROC/nP – Number of Processes
  • IO – Input/Output limits
  • a – average used
  • l – limit set for the account
  • m – maximal used
  • f – failure

That’s all.

You can contact our support for further assistance.