Plans & Getting Started

Understanding Hosting Resource Limits (CloudLinux)

By the Domain India teamPublished 6 min read
Knowledge base article
Contents (8 sections)

Every Domain India shared hosting account has its own share of the server, called its resource limits. Knowing what each limit measures, and what happens when you hit it, tells you what a slow page or an error really means.

Checking your own usage

To see your account's usage and faults, follow How to check your hosting resource usage. If visitors are seeing "Resource Limit Is Reached", go straight to Understanding and troubleshooting the "Resource Limit Is Reached" error.

Key takeaways

Our shared servers run CloudLinux, which puts each account in its own Lightweight Virtual Environment (LVE) with limits for CPU, physical memory, entry processes, number of processes, I/O and IOPS. Hitting the CPU or I/O limit slows your site down; hitting entry processes shows visitors a 508 "Resource Limit Is Reached" page; hitting memory or number of processes causes 500 or 503 errors. Disk space and file count are separate storage limits.

1. Why shared hosting has limits

Domain India shared hosting runs on CloudLinux (measured on our cPanel and DirectAdmin servers, 20 September 2026). CloudLinux wraps each account in its own Lightweight Virtual Environment, or LVE, with fixed limits. One busy or hacked site cannot slow down every other site on the server. The trade-off is that your site is held to its share even when the server has room to spare.

2. The limits, one by one

LimitWhat it measuresWhat happens when you hit it
CPUProcessor time used by your PHP scripts, cron jobs and other processesThe site slows down but still loads
Physical memoryRAM used by all your account's processes togetherA process is stopped; visitors may see a 500 or 503 error
Entry processesPHP requests running at the same momentNew requests get a "Resource Limit Is Reached" (508) page
Number of processesEverything running under your account, including cron jobs and SSH sessionsNew processes can't start; 500 or 503 errors, failed cron jobs
I/OHow fast your account reads and writes to diskDisk work slows; imports, backups and busy databases drag
IOPSHow many disk reads and writes per secondThe same slow-down, from many small operations

Entry processes are not visitors

This is the limit people misread most. An entry process is one web request that is running PHP right now. A cached page, an image or a stylesheet does not take one. A PHP page that finishes in a fraction of a second frees its slot almost at once; a page waiting on a slow payment or SMS service holds its slot the whole time. So a site with a few visitors can still run out if each request is slow, and a site with many visitors may never hit the limit if its pages are cached. Cron jobs and SSH sessions count towards number of processes, not entry processes.

Account memory is not PHP's memory_limit

The physical memory limit covers everything your account runs together. The PHP message "Allowed memory size exhausted" is different: it comes from a single script's own memory_limit setting. For that one, see How to fix "Allowed memory size exhausted" PHP errors.

3. Disk space and file count

Disk space and inodes (the number of files and folders) are storage limits, not LVE limits, but they fail just as hard. When either is full, uploads, new email and database writes fail. Old backups, unused installs, cache folders and mail you no longer need are the usual culprits.

4. What a fault is

A fault is one moment when your account reached a limit. A few during a genuine traffic spike are normal; faults every day need fixing, and the resource that faulted tells you where to look:

CPU or I/O faults
Heavy plugins, slow database queries, uncached pages, imports or backups at busy times.
Entry-process faults
Too many slow PHP requests at once: bots, login attacks, outside calls with no timeout.
Memory faults
Imports, image processing, or plugins that load large amounts of data.
Faults with low CPU and memory
Requests were waiting, not working. A bigger plan will not fix this.

5. How to stay inside your limits

Cache your pages (our shared hosting runs Apache, so on WordPress use WP Super Cache or W3 Total Cache), block abusive bots and login attacks, run heavy jobs at quiet hours, set a timeout of a few seconds on every outside call, and remove heavy plugins one at a time. The detail for each is in My website is slow and the "Resource Limit Is Reached" guide.

6. When to upgrade

Upgrade when faults continue after you have fixed the causes, or when genuine traffic has grown. An active cPanel or DirectAdmin plan can be upgraded at any time: open Hosting › My hosting, select your hosting service and choose Change plan. You pay only the difference for the time left until your renewal date, plus 18% GST, and the new limits apply as soon as that invoice is paid. Webuzo and Windows customers should contact support first.

cPanel Growth
₹200/mo + GST
  • 50 GB NVMe SSD Storage
  • 100 GB Monthly Bandwidth
  • 5 Websites
  • 50 Email Accounts
See plan details

The price on the card is live and excludes 18% GST. A VPS has no shared-hosting limits: you get dedicated vCPU and RAM and tune the server yourself.

What are resource limits on shared hosting?

They are your account's fixed share of the server. Domain India shared hosting runs on CloudLinux, which gives each account its own limits for CPU, physical memory, entry processes, number of processes, I/O and IOPS, so one busy site cannot slow down the others.

What is an entry process?

An entry process is one web request running PHP at that moment. Cached pages, images and stylesheets do not use one. When all your account's entry processes are busy, new requests get a 508 "Resource Limit Is Reached" page until some finish.

What happens when I hit the memory limit?

The process that pushed your account over the limit is stopped, and visitors may see a 500 or 503 error. This is different from PHP's "Allowed memory size exhausted" message, which comes from one script's memory_limit setting.

Do cron jobs count as entry processes?

No. Cron jobs and SSH sessions count towards your number-of-processes limit and use CPU, memory and I/O. Entry processes count only web requests running PHP.

How do I find out my account's exact limits?

Open a support ticket and we will tell you your account's current limits and read its usage and faults with you.

Ready to see where your site stands? Follow How to check your hosting resource usage, or open a ticket and we will read your account's numbers with you.

Not sure which limit you are hitting?

Tell us when the problem happened and which page was affected, and we will check your account's usage and faults with you.

Open a support ticket

Ready when you are

Get cPanel hosting from ₹125/mo + GST

See plans

Was this article helpful?

Your answer helps us decide what to improve next.

Still need help? Open a support ticket and our team will reply.

Prefer an app? Add this site to your home screen.Get the app
Understanding Hosting Resource Limits | Domain India