CloudLinux Resource Limits – CMS Hosting Packages Print

CloudLinux Resource Limits – CMS Hosting Packages

This article defines the standard CloudLinux LVE resource limits applied to LankaHost CMS hosting packages.

These limits are designed to provide sufficient resources for normal WordPress, PHP and supported Node.js workloads, while preventing a single hosting account from consuming excessive server resources and affecting other customers on the shared hosting platform.

Resource Limit Summary

Default additional settings:

• VMEM: 0
• IOPS: 1024 unless a package-specific value is configured

VMEM should normally remain disabled and PMEM should be used to control account memory usage.

CMS 2 GB

Recommended Limits:

This is the entry-level CMS hosting package and should remain comparatively restrictive. It is suitable for small WordPress websites, company websites, blogs and lightweight CMS applications.

The limits are intentionally configured to prevent entry-level accounts from consuming excessive CPU, memory or process capacity.

CMS 5 GB

Recommended Limits:

• CPU: 200%
• PMEM: 1.5 GB
• IO: 4 MB/s
• EP: 40
• NPROC: 120

This package provides additional resources for larger websites, plugins and applications with higher traffic or more dynamic content.

CMS 10 GB

Recommended Limits:

• CPU: 300%
• PMEM: 2 GB
• IO: 8 MB/s
• EP: 50
• NPROC: 150

This package is suitable for larger WordPress installations, WooCommerce sites and CMS applications with higher traffic or more resource-intensive plugins.

CMS 15 GB

Recommended Limits:

• CPU: 400%
• PMEM: 2 GB
• IO: 8 MB/s
• EP: 50
• NPROC: 180

This is the highest standard CMS shared-hosting tier. Although this package receives significantly more CPU capacity, resource limits must still be maintained to protect the overall shared-hosting environment.

Customers consistently requiring resources above these levels should be reviewed for migration to a VPS, cloud server, dedicated server or another higher-capacity hosting solution.

Understanding CloudLinux Resource Limits

CPU / SPEED

CPU limits control how much processor capacity an account can consume.

When an account attempts to consume more CPU than its assigned allocation, CloudLinux throttles the account rather than allowing it to consume unrestricted server resources.

CPU limits are particularly important for:

• WordPress plugins
• PHP applications
• Node.js applications
• WooCommerce
• Image processing
• Scheduled tasks
• Imports and exports
• Application builds
• Compromised websites
• Malicious or excessive traffic

PMEM – Physical Memory

PMEM controls the maximum amount of physical memory that processes belonging to a hosting account may consume.

For example, a PMEM limit of 1 GB means processes running under the account can collectively consume approximately 1 GB of physical memory.

PMEM is particularly important for Node.js applications because Node.js processes are normally persistent and remain active in memory.

IO – Disk Throughput

IO controls the maximum disk read/write throughput available to an account.

For example, an IO limit of 4 MB/s allows the account to perform disk operations at up to approximately 4 megabytes per second.

IO limits help protect the server from workloads such as:

• Large backups
• Archive extraction
• WordPress migrations
• Database exports
• Excessive logging
• Cache generation
• File scanning
• Malware activity

EP – Entry Processes

EP represents the maximum number of concurrent entry processes entering the account's CloudLinux LVE environment. It is particularly relevant to dynamic PHP and WordPress requests.

For example, an EP value of 30 allows approximately 30 concurrent entry processes.

When the EP limit is reached, the website may display an error such as:

508 Resource Limit Is Reached

High EP usage may indicate:

• High legitimate traffic
• Slow PHP execution
• Slow database queries
• Bot traffic
• Brute-force attacks
• Poorly designed plugins
• Disabled or ineffective caching

Important: EP should not be interpreted as the maximum number of visitors a website can support. A website can serve significantly more visitors because requests normally complete quickly.

NPROC – Number of Processes

NPROC limits the total number of processes and threads that can run under a hosting account.

Processes may include:

• PHP workers
• Node.js processes
• Cron jobs
• Background processes
• Shell commands
• Python processes
• Application workers

NPROC provides protection against applications that accidentally or deliberately create excessive numbers of processes.

This is particularly relevant for Node.js applications using worker processes, child processes, cluster mode, queue workers or other background services.

Node.js Hosting Considerations

Node.js behaves differently from traditional PHP applications.

A single Node.js process can handle many simultaneous connections using its event loop. Therefore, EP does not necessarily represent Node.js HTTP concurrency in the same way it does for PHP.

For Node.js applications, the most important CloudLinux limits are generally:

• CPU
• PMEM
• NPROC

Support staff should pay particular attention to Node.js applications that:

• Run multiple worker processes
• Use cluster mode
• Create child processes
• Run persistent background workers
• Perform CPU-intensive processing
• Perform image or video processing
• Run application builds
• Show continuously increasing memory usage

When a Customer Reaches a Resource Limit

Occasionally reaching a resource limit does not necessarily indicate abuse. Short resource spikes may occur during legitimate operations such as:

• WordPress updates
• Plugin updates
• Application deployments
• Backups
• Imports
• Traffic spikes

However, continuous or repeated resource-limit events should be investigated.

Support staff should review:

• CPU usage
• Memory usage
• Entry Processes
• Process count
• Disk IO
• Website access logs
• Cron jobs
• WordPress plugins
• Node.js workers
• Background processes
• Bot traffic

Abuse and Resource Management

Customers should not continuously consume their maximum allocated resources in a way that negatively affects the shared-hosting platform.

Examples requiring investigation include:

• Sustained CPU saturation
• Continuous EP exhaustion
• Excessive NPROC usage
• Uncontrolled Node.js workers
• Excessive background processing
• Compromised WordPress websites
• Excessive cron execution
• Mass mailing
• Large automated scraping workloads
• Cryptocurrency mining

Where necessary, LankaHost Support may temporarily restrict an application, request corrective action, recommend application optimisation or require migration to a more appropriate hosting service.

Package Upgrade Guidance

A package upgrade may be appropriate when a legitimate website consistently reaches its assigned resource limits. However, support staff should determine whether the issue is caused by application inefficiency before recommending an upgrade.

For example, continuously reaching the CPU or EP limit because of a compromised or poorly configured WordPress plugin should be resolved by fixing the website rather than simply increasing the available resources.

Customers requiring sustained resources beyond the CMS 15 GB package should generally be considered for:

• VPS Hosting
• Cloud Server
• Dedicated Server
• Custom Hosting Environment

Internal Configuration Standard

Last reviewed: September 2026
Applies to: LankaHost cPanel / CloudLinux CMS Shared Hosting Platform