Current stats
Live CPU, RAM, IO, PIDs, and EP across users—including DB-attributed metrics when governor is active.
cGroup resource limits
Stop noisy neighbors with package-based CPU, memory, IO, and process controls powered by Linux cGroups v2.
Packages
Package-based control that sticks
Create reusable limit packages for shared, reseller, and premium tiers. Apply defaults globally, map to panel plans, or override individual accounts when needed.
- CPU quota (percentage of CPU time)
- Memory high (throttle) and max (hard limit)
- IO read/write bandwidth
- IOPS read/write caps
- Tasks / PID maximums
- Entry processes (EP) style concurrency limits
Visibility
Observe what you enforce
Limits without observability create guesswork. Simuzo pairs packages with live and historical metrics.
History
Configurable collection interval and retention for capacity trends and plan design.
Faults & top consumers
See who hits limits and who drives load so you can upgrade plans or investigate abuse.
Enforcement
Process assignment that keeps limits real
simuzo-procmon helps keep user processes in the correct cgroup hierarchy so limits apply to web, cron, and other workloads consistently.
- CLI reload for fleet-wide package updates
- Plan defaults plus per-user overrides
- Works alongside SimuzoFS isolation
FAQ
Common questions
Which controllers are supported?
Simuzo uses Linux cGroups v2 controllers for CPU, memory, IO (bandwidth and IOPS), and PIDs, plus entry-process tracking for concurrent connection style limits.
Can limits differ by hosting plan?
Yes. Define packages (including a default) and map them to panel plans or set custom per-user overrides that take priority.
How do I see who is hitting limits?
Use Statistics for live usage, historical trends, fault records, and top consumers—then adjust packages or investigate noisy accounts.
Ready to secure your hosting nodes?
Install Simuzo on your panel server, enable isolation and limits, and give users a safer multi-tenant environment.