Resource Usage: understand CPU, memory, I/O and entry-process faults

Shared servers divide resources among accounts. A server’s processor count and installed RAM are not the amount assigned to each hosting customer. Resource Usage helps you see the account’s actual constraints.

Investigate a slow period

1. Record when the problem occurred and which application or task was active.
2. Open Resource Usage and choose the relevant time range.
3. Inspect CPU, memory, I/O and process indicators available on your host. Look for limit faults, not only averages.
4. Compare the time with backups, imports, scheduled jobs, traffic spikes and application errors.
5. Reduce avoidable work, then monitor the same workload before requesting a larger package.

Different limits need different fixes

Slow database queries, excessive uncached requests or an expensive plugin may consume CPU. Many concurrent requests can exhaust entry-process capacity. Large image decoding and imports can pressure memory. Raising PHP memory_limit cannot increase the account’s physical RAM allowance.

Keep private pages and customer-specific responses out of shared public caches. Stagger heavy scheduled tasks and avoid repeatedly running backups while diagnosing load. Ask support to interpret unfamiliar metrics and provide the timestamp and workload. Upgrade capacity when measured normal demand exceeds the plan, rather than assuming every slow page needs more RAM.