Hosting resource usage is not just about disk space. CPU, RAM, disk I/O, entry processes, and inode counts can all affect whether a site runs smoothly.
CPU
CPU is used when PHP executes, pages are built, images are processed, backups run, or background tasks fire. Heavy plugins and uncached pages can increase CPU use.
RAM
RAM is working memory. Applications need enough memory to run requests, process uploads, and complete scheduled tasks. PHP memory limits affect individual PHP processes.
Disk I/O
I/O measures reading and writing to disk. Backups, cache rebuilds, large imports, and busy databases can increase I/O.
Inodes
An inode roughly represents a file or directory. A site with many tiny cache files can hit inode limits even if total disk usage looks modest.
What to Do
Enable caching, remove unused files, clean old backups, optimise images, and review plugins. If legitimate traffic has outgrown the plan, it may be time to upgrade.
Resource graphs are clues. Match spikes to real events such as backups, campaigns, imports, or plugin updates.
CPU and Memory Show Different Pressure
CPU reflects processing work such as PHP, image conversion and database queries. Memory holds running processes and cached data. A brief peak may be normal; sustained saturation, killed processes or repeated out-of-memory errors need investigation. Raising one limit does not repair inefficient code.
IO and Inodes Affect Storage Work
IO limits how quickly data is read or written, while inode usage counts filesystem objects. Millions of cache, session or email files can exhaust inodes despite free disk space. Identify the generating application before deleting data and exclude disposable caches from backups where appropriate.
Correlate Before Upgrading
Compare timestamps with traffic, cron, backups, imports and deployments. Inspect slow queries and application logs. Optimise legitimate waste first, then upgrade when normal demand consistently approaches a defined limit and the larger plan provides the constrained resource.
