Understanding CloudLinux Resource Limits
CloudLinux is the operating system on our shared hosting servers that isolates each account and enforces fair resource limits. Understanding these limits helps you optimize your website performance and avoid hitting resource caps.
What Is CloudLinux?
CloudLinux uses a technology called LVE (Lightweight Virtual Environment) to allocate specific resource limits to each hosting account. This ensures:
- No single account can affect other users on the server
- Resources are fairly distributed
- Server stability is maintained
Resource Types
| Resource | Description | What It Affects |
|---|---|---|
| CPU | Processing power (measured in cores/percentage) | Script execution, database queries |
| Physical Memory (PMEM) | RAM allocated to your account | PHP processes, database connections |
| I/O | Disk read/write speed (MB/s) | File operations, database reads/writes |
| IOPS | Input/Output operations per second | Number of file operations |
| Entry Processes (EP) | Concurrent PHP/CGI processes | Simultaneous visitors |
| Number of Processes (NPROC) | Total processes allowed | All running processes |
Checking Your Resource Usage
Via DirectAdmin
- Log in to DirectAdmin
- Look for Resource Usage or CloudLinux LVE Statistics in the dashboard
- You will see current and historical usage for all resource types
Via SSH
lveinfo --display-usernameThis shows your current resource allocation and usage.
Understanding the Metrics
Current Usage
Shows real-time resource consumption. If any metric reaches 100%, requests may be queued or rejected.
Faults
A fault occurs when your account hits a resource limit. The system records:
- Number of faults per resource
- Timestamp of each fault
- Duration of the limit being hit
Tip: Occasional faults during traffic spikes are normal. Frequent faults indicate you may need to optimize your site or upgrade your plan.
Common Causes of Resource Limit Issues
High CPU Usage
- Unoptimized PHP scripts or database queries
- Too many WordPress plugins
- Missing database indexes
- Bots and crawlers hitting your site excessively
High Memory Usage
- PHP memory_limit set too high
- Memory leaks in custom scripts
- Large image processing operations
- Too many concurrent PHP workers
High I/O
- Large database operations
- Frequent disk writes (logging, caching)
- Backup operations running during peak hours
High Entry Processes
- Too many concurrent visitors
- Slow PHP scripts holding connections open
- Missing caching (every visitor runs PHP instead of serving cached pages)
Optimizing Resource Usage
- Enable caching — Use a caching plugin (WP Super Cache, LiteSpeed Cache) to serve static pages
- Optimize images — Compress images before uploading; use lazy loading
- Minimize plugins — Remove unused WordPress plugins and themes
- Optimize database — Clean up post revisions, spam comments, and transient data
- Use a CDN — Offload static assets to reduce server load
- Block bad bots — Use robots.txt or security plugins to block aggressive crawlers
- Optimize queries — Add proper indexes to database tables
When to Upgrade
Consider upgrading your hosting plan if:
- Resource faults occur regularly (multiple times per day)
- Your website frequently returns 503 or 508 errors
- Pages load slowly despite optimization
- You are running multiple resource-intensive applications
Related Articles
Need help? Contact our support team at {{SUPPORT_EMAIL}} or open a ticket at {{SUPPORT_URL}}.