CloudLinux LVE (Lightweight Virtual Environment) applies real-time caps per hosting account. When you edit packages in LVE Manager (WHM), you are deciding how much of the server each plan may use before it is slowed — not killed blindly.
The limits you will set most often
- CPU: relative CPU share; burst settings control short spikes
- IO: disk bandwidth so one backup-heavy site cannot starve others
- PMEM / VMem: physical and virtual memory ceilings
- EP (entry processes): concurrent connections into PHP/web for that user
- nPROC: process count caps to stop fork bombs and runaway cron storms
Practical defaults
Start conservative on entry-level plans, then raise limits for “business” packages after you watch real traffic for a week. Document what each plan means so support can explain throttling to customers (“your site hit EP, not the whole server died”).
License note
LVE only helps if CloudLinux is licensed and healthy. Keep your CloudLinux license active and avoid mystery kernel “fixes” from random blogs — prefer vendor docs and ticket support when nodes misbehave.