CPU, RAM and bandwidth: understanding hosting resource limits

Hosting plans are sold with a neat list of numbers: 1 CPU core, 2 GB RAM, unmetered bandwidth, 25 entry processes, 250,000 inodes. Most website owners tick the plan that sounds big enough and never look at those figures again, until something slows down. This guide explains what hosting resource limits actually control, which ones matter for a typical business website, and how to read the usage graphs your host already gives you.

You do not need to be a server administrator to follow along. If you can log in to cPanel, DirectAdmin, Plesk or your host’s own dashboard, you have everything required.

Why hosts put limits on resources at all

On shared hosting, dozens or even hundreds of accounts live on one physical server. Without caps, one busy or badly coded site could consume all the processing power and drag every neighbour down with it. Limits keep things fair.

Many shared hosts use account isolation software, such as CloudLinux LVE, to enforce these caps per account. On a VPS or dedicated server the limits are simply the size of the machine you rented, but the same resources still run out in the same ways.

CPU: how fast your site can think

The CPU does the actual work of building each page. When someone opens a product page on a WordPress or Laravel site, PHP code runs, the database is queried, and HTML is assembled. All of that consumes CPU time.

Plans usually express CPU as a number of cores or as a percentage, where 100% equals one full core. A plan offering 100% CPU lets your account use up to one core’s worth of processing at any moment.

What uses CPU on a normal website

• Generating uncached pages, especially search results and filtered product lists
• Admin tasks such as bulk imports, backups and image resizing
• Scheduled tasks and plugin housekeeping
• Bots crawling large numbers of pages in a short time

Static files like images, CSS and JavaScript need very little CPU. That is why page caching, which serves a saved copy instead of rebuilding the page, reduces CPU use so much.

RAM: how much the site can hold in mind at once

Memory is where running processes keep their working data. Each PHP request needs some RAM while it runs, and the database server keeps frequently used data in memory for speed.

Two separate numbers are easy to confuse. The account RAM limit is the total memory all your processes may use together. The PHP memory_limit is the maximum a single PHP script may use. A site can hit one without touching the other. For example, a single heavy report can fail with an “Allowed memory size exhausted” error while total account memory looks fine.

Bandwidth and data transfer

Bandwidth, more accurately called data transfer, is the amount of data sent from your server to visitors over a month. Every page view, image download and PDF counts.

A rough way to estimate it: multiply your average page weight by monthly page views. A 2 MB page viewed 20,000 times a month transfers about 40 GB. Hosting images on a CDN such as Cloudflare can shift a large share of that away from your server.

“Unmetered” or “unlimited” bandwidth usually still sits under a fair use policy. In practice, CPU or entry process limits tend to become the real ceiling long before data transfer does.

Entry processes and inodes on shared hosting

These two limits appear mostly on shared plans and puzzle almost everyone the first time.

Entry processes

An entry process is roughly one PHP request being handled at the same moment. If your limit is 20, the server can process 20 dynamic requests for your account simultaneously. The 21st waits or receives an error, often a 508 “Resource Limit Is Reached” page.

Entry processes are not the same as visitors. A person reading a page uses nothing. Only the brief moment when the server generates a response counts. A fast, cached site with 20 entry processes can serve far more than 20 people at once.

Inodes

An inode is one file or folder. Every image, email message, cache file and plugin file counts as one. A plan with a 250,000 inode limit can store that many items regardless of their size.

Inode counts creep up quietly through old backups kept on the server, thousands of cache files, full mailboxes and multiple thumbnail sizes generated for each uploaded image. Hitting the limit can stop uploads, emails and even backups from working.

How to read your hosting usage graphs

In cPanel on CloudLinux servers, look for a section called Resource Usage. Other panels have similar pages. You will typically see graphs for CPU, physical memory, entry processes, number of processes and I/O, each with a line marking your limit.

1. Set the time range to a week or a month. A single day hides patterns.
2. Look for flat tops. A line that runs along the limit ceiling means the account was throttled at that time.
3. Check the faults column. Most panels count how many times each limit was hit. A handful of faults a month is normal; hundreds a day is not.
4. Match spikes to events. Did usage jump when a newsletter went out, a sale started or a nightly backup ran?
5. Compare average with peak. Low averages with sharp peaks suggest a scheduled task or crawler, not a plan that is too small.

Disk space and inode usage are usually shown separately, often in the sidebar statistics on the main panel page.

Which limit matters most for your kind of site

Different websites stress different resources:

• Brochure or company sites rarely stress anything once caching is on. Inodes from email are the usual surprise.
• Online stores push CPU and entry processes because carts, checkout and filtered searches cannot be fully cached.
• News portals and blogs with heavy images need bandwidth and disk, and see entry process spikes when a story is shared widely.
• Custom web apps with dashboards and reports tend to need more RAM per request.

Choosing a plan that fits your real usage

Spend a few minutes this week opening your resource usage page and noting your typical and peak figures for CPU, RAM and entry processes, plus your inode count. Keep those numbers somewhere handy. When you next compare plans, you will be matching real data instead of guessing from marketing tables.

If your graphs regularly touch the ceiling even after caching and clean-up, it may be time to move from shared hosting to a VPS hosting plan with dedicated resources. Our team is happy to look at your usage figures with you through our support desk before you decide.

Frequently asked questions

Is 1 GB of RAM enough for a WordPress website?

For a small, well-cached WordPress site on shared hosting, 1 GB of account memory is often workable. Stores with WooCommerce, page builders or many plugins usually benefit from 2 GB or more, especially during busy periods.

Does unlimited bandwidth mean I can have unlimited visitors?

No. Data transfer might not be capped, but CPU, RAM and entry processes still are. Those limits decide how many simultaneous requests the site can handle.

How do I check how many inodes my hosting account uses?

In cPanel, the statistics panel on the home screen usually shows “File Usage” with your inode count and limit. Many other control panels show it under disk usage or account statistics.

What is the difference between physical memory and virtual memory in cPanel?

Physical memory is the actual RAM your processes are using. Virtual memory includes memory that processes have reserved but may not be actively using. Physical memory is normally the more useful figure to watch.