Setting resource limits on an account
How to adjust or override the resource limits for one specific hosting account.
While a package sets the default limits for every account that uses it, sometimes you need to adjust CPU, memory, or the process limit for one particular account without changing its package, for example giving a busy customer more headroom, or capping an account that's using more resources than expected.
Steps
- Click Users & Resellers in the sidebar and find the account you want to adjust.
- Click Manage on its row, then open the Limits tab.
- Adjust the CPU, memory, process limit, disk I/O priority, disk speed, and disk operations figures as needed.
- Make sure Apply CPU and memory limits when saving is ticked, then click Save all changes.
These four (CPU, memory, disk I/O priority, and process limit, along with disk speed and disk operations) override whatever the account's package would otherwise give it, but only while that tick box is checked. Everything else a package sets, disk space, file count, outbound emails an hour, databases, websites, subdomains, mailboxes, and scheduled jobs, has no per-account override here and always comes from the package. To change one of those, move the account to a different package instead.
What each limit controls
- CPU and memory: how much processing power and system memory the account's websites may use at once, which keeps one busy account from slowing down others on the same server. Both are chosen from a dropdown scaled to this server's own core count and RAM.
- Process limit: the maximum number of simultaneous processes the account may run, which protects the server against a runaway script or application spawning too many at once. Set it to 0 to use the server default, or tick No limit at all to remove this protection entirely for a real workload, such as a large build, that genuinely needs it. Only do this for an account you trust, since with no limit a runaway process can slow down or crash the server for everyone.
- Disk I/O priority: Low, Normal, or High, which decides who goes first when two accounts want the disk at the same moment. It's a share, not a hard cap.
- Disk speed and disk operations a second: hard caps (0 means no cap) on how much data, and how many separate reads or writes, this account may make each second.
When these limits don't apply yet
CPU, memory, and process limits only reach an account's websites once it has its own PHP program (isolated PHP). Every package now includes this, so a newly created account already has it; the Limits tab shows plainly whether it's currently on for the account you're managing.
Putting a whole reseller's customers under one shared ceiling
A package limit applies to each account on its own: a reseller with fifty customers on a package capped at 10MB/s disk speed has fifty accounts that may each individually do 10MB/s. That stops any one customer taking over the machine, but does nothing to cap the reseller as a whole.
Combined limits per reseller, found under Users & Resellers → Tools, puts all of a reseller's accounts under one shared ceiling instead, for CPU, memory, disk speed, disk operations a second, and process count. Their customers' own per-account limits still apply inside it, whichever runs out first for a given account is the one that bites.
- Click Users & Resellers in the sidebar, then the Tools tab.
- Find Combined limits per reseller, choose the reseller, and tick Apply a combined cap to this reseller.
- Set a CPU share (100 is one full core, so 400 gives all of their customers four cores between them), Memory, Disk speed, Disk operations a second, and Processes. Leave any of them at 0 for no cap on that one.
- Click Apply to this reseller and confirm. Every one of that reseller's accounts is moved under the shared cap in the background, one at a time, their sites keep serving throughout.
To remove it, return to the same row, untick Apply a combined cap to this reseller, and save, their accounts go back to each having their own, individual limits.
This is a different setting from a reseller's own disk space, bandwidth, and account allowance, which they hand out to their own packages, see the reseller article on understanding their allowance for that one.