CPU, memory and process limits per hosting account

For server administrators · Updated 2026-10-29

On this page
  1. The three limits
  2. What counts
  3. Change the limits
  4. Where you see it
  5. Common questions

Every package has three server-resource limits. They keep one busy or hacked website from slowing down all the others. The kernel enforces them for each account separately.

The three limits

Field in the packageWhat it limitsAt the limit
Processor (% of one core)CPU time. 100 = one full core, 200 = two cores, 50 = half a core.The account is slowed down. Nothing is stopped.
Memory (MB)Memory of all the account's processes together.Only the account's biggest process is stopped.
ProcessesHow many processes the account may run at once.New processes cannot start until others end.

Enter 0 for unlimited. A new package starts at 100%, 1024 MB and 100 processes.

What counts

PHP of the websites, cron jobs, SSH and terminal sessions, and Node.js, Python or Ruby applications of the account all count against the same limits. Other accounts are never affected when one account reaches its limits.

Change the limits

  1. Open Packages (section Accounts) and click Edit next to the package.
  2. Change Processor (% of one core), Memory (MB) or Processes.
  3. Click Save changes.

The new limits apply at once to every account on the package. To give one account more, move it to another package: see change the package.

Where you see it

  • Customers: Resource Usage (section Advanced) in the control panel shows the limits, the memory and processes in use now, and a table of the last 7 days with CPU time, Peak memory, Peak processes and Limits reached (for example slowed 3.5 min, 2× memory).
  • Administrators: Server Status → Daily process log lists every account's CPU time, average CPU, peak memory, peak processes and the limits reached, for each of the last 90 days.

Common questions

A website is slow but the server is idle. Why?

The account may be at its processor limit. Look at Limits reached in its Daily process log row. If it shows "slowed", raise Processor (% of one core) or optimise the site.

A PHP page sometimes fails with an error 500 or a blank page. Could it be memory?

Yes, if Limits reached shows "memory": the biggest process of the account was stopped because the account used all of Memory (MB). Raise the memory limit or lower the site's memory use.

Is there swap for an account over its memory limit?

No. When a memory limit is set, the account cannot use swap; its biggest process is stopped instead.

Was this article helpful?

Still stuck?

Ask the AI about your exact situation — it answers from this knowledge base — or contact us.