How do I change the CPU or Memory limit for each cPanel account? Print

  • 1

Our cPanel Cloud Hosting / Cloud Reseller Hosting allows you to set individual CPU and RAM limit for each of your cPanel account or packages. 

If this is supported in your hosting plan, you will see the option in your WHM > CloudLinux Manager page.

You will find at least six tabs in your CloudLinux Manager page, some of which may be hidden in the hamburger (three dot) menu depending on your screen size and resolution:

  • Current Usage
  • Historical Usage
  • Users
  • Statistics
  • Options
  • Packages

IMPORTANT: You are only allowed to change the CPU (SPEED) and Memory (PMEM) limit. All the other limits must remain untouched.


Current Usage

The Current Usage tab shows the realtime resource usages of your cPanel accounts. 

  • SPEED = CPU Usage
  • PMEM = Memory Usage
  • IO = Disk I/O Usage
  • IOPS = IOPS Usage
  • EP = Entry Processes Usage
  • NPROC = Total Processes Usage

Historical Usage

The Historical Usage tab shows the previous usages of your accounts along with the graph.

You can use the Timeframe dropdown to view past usages for your accounts.

Once you have some usages here, you should also see your plan's overall CPU and Memory limit.


Users

The Users tab shows the default limit assigned to each of your cPanel account.

You can manually change the limit for any account or you can change the DEFAULT limit which will apply to all your accounts.

You can set the CPU (SPEED) and Memory (PMEM) to any limit of your choice but your total usage across all accounts will not exceed your plan's overall limit.

To change the CPU limit of a user / cPanel account, modify the SPEED limit like these examples:

  • 100% = 1 CPU Core
  • 200% = 2 CPU Cores
  • 300% = 3 CPU Cores

To change the Memory limit of a user / cPanel account, modify the PMEM limit like these examples:

  • 1G = 1 GB RAM
  • 2G = 2 GB RAM
  • 3G = 3 GB RAM

IMPORTANT: You are only allowed to change the CPU (SPEED) and Memory (PMEM) limit. All the other limits must remain untouched.


Statistics

The Statistics tab allows you to list the resource usage of your cPanel accounts and sort them via Timeframe, Limit and more. 

You can also click on the graph icon for each domain to view the individual CPU usage for each cPanel account. This is the same graph that you can view if you login to the individual cPanel account > Resource Usage page.


Options

The Options tab allows you setup notifications if you or your cPanel accounts hit any of the limits.

It also provides granular options like which faults to include and the minimum number of faults before a notification is sent. 

A "fault" is an incident where an account hit any of the resource limit.


Packages

The Packages tab allows you to set different CPU (SPEED) and Memory (PMEM) limit for each of your hosting package. 

The hosting packages are created in your WHM > Add a Package page and they can be assigned to a cPanel account in your WHMUpgrade/Downgrade an Account page.

To change the CPU limit of a hosting package, modify the SPEED limit like these examples:

  • 100% = 1 CPU Core
  • 200% = 2 CPU Cores
  • 300% = 3 CPU Cores

To change the Memory limit of a hosting package, modify the PMEM limit like these examples:

  • 1G = 1 GB RAM
  • 2G = 2 GB RAM
  • 3G = 3 GB RAM

IMPORTANT: You are only allowed to change the CPU (SPEED) and Memory (PMEM) limit. All the other limits must remain untouched.


Other LVE Limits

Besides the CPU and RAM limits which you can configure, the other limits below are fixed on a per cPanel account basis and must remain untouched:

  • IO - 25 50 MB/s
  • IOPS - 1024 2048
  • EP - 25 30
  • NPROC - 100

These limits are more than enough for most websites and they are mainly set as a sanity limit to prevent abuse or runaway scripts from causing issues. 

We do revise these limits (usually upwards) from time to time and they are retroactively applied to all cPanel accounts. 

Inodes: We do not have a fixed inodes limit as long as your usage is reasonable. We will be in touch if your inodes usage is too high to the point that it can cause issues to the server.


Was this answer helpful?

« Back