All PiviHost shared hosting plans use CloudLinux LVE to ensure stability, fairness, and predictable performance for every customer.
Each hosting account is assigned clearly defined resource limits, enforced automatically and in real time.
Per-Account Resource Limits (Example: Tucana Plan)
| Parameter | Description | Limit |
|---|---|---|
| CPU (SPEED) | Maximum CPU usage | 100% (1 core) |
| CPU MySQL | Maximum CPU usage for MySQL queries | 100% |
| Physical Memory (PMEM) | Maximum physical RAM | 1 GB |
| Disk I/O | File system disk speed | 10 MB/s |
| MySQL Disk I/O | Disk speed for MySQL operations | 5 MB/s |
| IOPS | Disk operations per second | 1024 |
| Entry Processes (EP) | Concurrent PHP/web processes | 20 |
| Number of Processes (NPROC) | Maximum processes | 50 |
| Inodes (soft limit) | Warning threshold | 100,000 |
| Inodes (hard limit) | Maximum files | 150,000 |
| Virtual Memory (VMEM) | Virtual memory | Unlimited |
Higher hosting plans include increased limits.
Why Resource Limits Exist
Resource limits:
-
prevent a single account from affecting others
-
provide predictable performance
-
protect server stability
-
ensure fair usage across all customers
This is standard practice on professional shared hosting platforms.
Key Notes
-
Limits apply per hosting account, not per website
-
Limits are enforced automatically
-
No penalties or fees apply for reaching limits
-
Upgrading a plan immediately increases limits
