CloudLinux Limits & LVE Manager

RemarkableCloud cPanel servers run CloudLinux, which uses LVE (Lightweight Virtual Environment) to isolate each hosting account in its own resource container. This prevents one account from slowing down or crashing others — a common problem on traditional shared hosting.

What LVE controls

Resource	What it limits
CPU	Percentage of one CPU core the account can use
PMEM	Physical RAM the account can consume
VMEM	Virtual memory limit (usually set to unlimited)
EP	Entry Processes — simultaneous incoming connections
NPROC	Number of processes the account can run simultaneously
IO	Disk read/write speed in KB/s
IOPS	Disk I/O operations per second

Accessing LVE Manager

Log into WHM → search LVE Manager → CloudLinux → LVE Manager.

The dashboard shows all accounts with their current limits and whether they've hit any limits recently (shown in red).

Default limits

RemarkableCloud sets these defaults on all servers. Adjust for your workload:

Resource	Default	Recommended for WooCommerce
CPU	100%	200–400%
PMEM	512 MB	1024–2048 MB
EP	20	40–60
NPROC	100	150
IO	1024 KB/s	2048–4096 KB/s

Adjusting limits for a specific account

1. In LVE Manager, click the Users tab.
2. Find the account you want to adjust — use the search box.
3. Click the Edit icon (pencil) next to the account.
4. Uncheck Use Default for the resources you want to customize.
5. Enter the new values.
6. Click Save.

Setting server-wide defaults

To change the default limits applied to all accounts:

1. Go to LVE Manager → Options
2. Modify the default values
3. Click Save

Accounts with custom limits keep their custom values. Only accounts using defaults are affected.

Diagnosing limit hits

If a site is slow or returning 503 errors, check if it's hitting LVE limits:

1. Go to LVE Manager → Statistics
2. Set the time range to the period when slowness was reported
3. Look for accounts with high faults — these are limit hits

A high EP fault count means too many simultaneous connections. A high CPU fault count means the site needs more processing power.

You can also check from SSH:

# Current LVE usage for all accounts
lveps --cpu --mem --io

# Historical faults for a specific user
lveinfo --user=username --period=1d

Common limit issues and fixes

Site returns 503 errors under traffic Usually an EP (Entry Process) limit hit. Increase EP from 20 to 40–60 for the affected account.

WordPress admin is slow but frontend is fine Usually a CPU limit. Admin requests are heavier (more PHP, more DB queries). Increase CPU to 200% for the account.

File uploads fail or time out Can be an IO limit. Increase IO from 1024 to 2048 KB/s.

Database queries are slow Often PMEM — insufficient RAM forces MySQL to use swap. Increase PMEM and consider upgrading the Cloud Cube plan if the issue persists across multiple accounts.

✓

Monitor before raising limits blindly

Check statistics for 24–48 hours before increasing limits. An account consistently hitting 100% CPU may have runaway processes or malware — increasing limits just gives the problem more room. Investigate with Imunify360 first.