📦
Hosting

Hosting Plan Terms Explained: Disk, Inodes, CPU, RAM and Processes

16.11.2026
← All articles

A hosting plan table can look like a list of cryptic labels: disk, inodes, CPU, RAM, processes, databases. Many people choose by disk size alone and are then surprised when the site slows down with half the disk empty. Each figure describes a different server resource, and knowing which one your site depends on is the key to choosing the right plan.

Disk: space for files and databases

Disk space holds your site files, databases, mailboxes and often backups. A small business card site may need a few hundred megabytes, while a shop with hundreds of product photos or a school site full of event pictures quickly reaches gigabytes. Mailboxes usually count against the same disk, so staff keeping large attachments forever eat into your site's space. A full disk does more than block uploads: databases fail to write, cache files are not created and a CMS may half-write a configuration file and take the site down. Keeping 20-30 percent free is a good habit.

Inodes: a limit on the number of files

An inode is a file system record allocated for every file and folder, so an inode limit caps the number of files rather than their size. With 10 GB of disk and 200,000 inodes you can hit the file limit long before the disk fills. Typical culprits are plugins that never clean their cache, galleries generating thousands of thumbnails and session files that are never deleted. The symptoms match a full disk, which is confusing when the panel shows plenty of free space.

CPU: processor time

On shared hosting a server is divided among many customers and each account gets a share, often expressed as a percentage of a core. Every page view runs PHP code, queries the database and builds HTML, all of which uses CPU time. A WordPress site without page caching and with heavy plugins can hit the limit under ordinary traffic. When it does, the site usually slows down rather than stops, because the system queues your processes.

RAM: working memory

Each PHP process needs memory to handle a request, and tasks like large reports, image resizing or big imports need much more. If your account's processes exceed the memory limit, the system kills one of them and visitors see a 500 or 503 error. RAM matters especially for Python or Node.js apps, which run continuously and hold memory for long periods.

Processes and concurrent connections

Many plans limit how many processes can run at once. Each visitor request is served by a process or thread, and when concurrent visitors exceed the limit, extra requests wait or get a "resource limit reached" error. This shows up on sale days or when search bots crawl aggressively.

TermWhat it limitsSymptom when exhausted
DiskSize of files, databases, mailUpload errors, database write failures
InodesNumber of files and foldersFiles cannot be created despite free space
CPUProcessor shareSite slows down
RAMWorking memoryProcess killed, 500/503 error
ProcessesConcurrent requestsQueueing, resource limit errors

Measuring your own needs

If you have SSH access, these commands give the main picture:

# Folder sizes (largest at the bottom)
du -sh ~/* 2>/dev/null | sort -h

# Total number of files (roughly your inode count)
find ~ -xdev | wc -l

# Which folder holds the most files
cd ~ && find . -xdev -type f | cut -d/ -f2 | sort | uniq -c | sort -n | tail

# Your running processes
ps -u "$USER" -o pid,pcpu,rss,etime,cmd

Without SSH, check the resource statistics section of your hosting panel, which usually shows disk, inode and load graphs.

Example: a training centre in Andijan

An English language centre in Andijan used only 2 GB of disk, yet the site slowed every evening. The cause was CPU: blog pages were not cached and each visit ran dozens of queries. A caching plugin fixed that, but a month later the inode limit was hit because old cache files were never removed. A scheduled cache cleanup solved both problems without upgrading the plan.

When to upgrade

If resources stay at the limit after optimisation, identify which one is short. More disk needs a larger disk plan; constant CPU or RAM pressure calls for a stronger plan or a VPS. You can view and change your hosting plan in the sayt.uz cabinet and ask support about specific limits through a ticket.

Related articles

🔑 Enabling SSH on your hosting and connecting with a key 🛠️ Corrupted MySQL Table: How to Check and Repair It 🧩 Garbled characters on your site: causes and fixes for broken encoding 🛡️ Is your hosting backup enough? The 3-2-1 rule in practice
🌐 Language
🇺🇿 O'zbek 🇺🇿 Ўзбек 🇷🇺 Русский 🇬🇧 English ✓