Hosting resource limits explained: CPU, RAM, entry processes and I/O

What Are Hosting Resource Limits and Why Should You Take Them Seriously?

When a website runs on shared hosting or even a virtual private server (VPS), hardware resources such as the processor (CPU), memory (RAM), the number of concurrent processes (Entry Process), and disk input/output speed (I/O) are shared among users. Every hosting provider imposes limits on these resources to maintain service stability and prevent one site from affecting others. If these hosting resource limits are not properly understood, they can cause slowdowns, outages, or mysterious errors on your site. In this article, we will examine each limit in detail, including related errors and practical methods to reduce consumption.

CPU Limit in Hosting: Symptoms and Solutions

What Does CPU Limit Mean?

The CPU is the central processing unit that executes PHP commands, scripts, and web requests. In shared hosting, a specific percentage of a processor core's power is typically allocated to each account. For example, you might be allowed to use 25% of a CPU core. If your site consistently exceeds this quota, the hosting provider will limit or stop your processes.

Common Errors Caused by CPU Limits

• 503 Service Unavailable Error – The most common error when CPU usage is too high.
• "Resource Limit Is Reached" Message in cPanel or DirectAdmin control panels.
• Severe Site Slowness during peak traffic hours.

How to Reduce CPU Usage

1. Enable Caching: Use caching plugins like WP Rocket or W3 Total Cache for WordPress. Caching static pages can reduce CPU load by up to 80%.
2. Optimize the Database: Identify heavy MySQL queries using a plugin like Query Monitor. Do not neglect proper indexing on frequently used tables.
3. Reduce External Requests: Remove or limit unnecessary API calls. Each external request consumes a CPU cycle.
4. Use a CDN: Place static files (CSS, JS, images) on a CDN to reduce processing on the main server.

Troubleshooting Tip: In cPanel, check the "CPU and Concurrent Connection Usage" section. If CPU usage is consistently above 70% over 5-minute intervals, you need immediate optimization.

RAM Limit in Hosting: Symptoms and Solutions

What Does RAM Limit Mean?

RAM is temporary memory where active scripts and processes run. Each hosting account typically has a specific RAM ceiling (e.g., 1 GB). If your site exceeds this limit, processes will be killed.

Common Errors Caused by RAM Limits

• "Allowed memory size of X bytes exhausted" Error – This error appears directly in the PHP log.
• White Screen of Death (WSOD) in WordPress.
• Incomplete Page Loading or sudden processing interruptions.

How to Reduce RAM Usage

1. Optimize Images: Compress large images with tools like TinyPNG. A 2 MB image can consume up to 50 MB of RAM.
2. Remove Unnecessary Plugins: Each WordPress plugin occupies a portion of RAM. Remove heavy plugins like complex sliders.
3. Adjust PHP Memory Limit: Add the following line to your wp-config.php file:
   

   define('WP_MEMORY_LIMIT', '256M');

   This increases the allowed memory for PHP, but if the hosting does not have enough RAM, the error will persist.
4. Use Optimized Cron Jobs: Move heavy scheduled tasks to low-traffic hours.

Common Mistake: Some users set memory_limit in php.ini to 512 MB or more, while the hosting only provides 256 MB of dedicated RAM. This causes an "Out of memory" error. Always check the allowed limit with your hosting support.

Entry Process Limit: The Silent Killer of Busy Sites

What Does Entry Process Mean?

Entry Process refers to the number of concurrent processes your site can run. Each visitor, search engine bot, or AJAX request consumes one process. The typical limit is between 10 and 50 concurrent processes. If your site has 100 concurrent visitors but a limit of 20 processes, 80 people will encounter errors.

Common Errors Caused by Entry Process Limits

• 508 Resource Limit Is Reached Error – Specific to this limit.
• "Too many connections" Message in the database.
• Severe Slowness and Timeout during peak traffic.

How to Reduce Entry Process Usage

1. Enable Keep-Alive with Proper Settings: In your .htaccess file:
   

   Header set Connection keep-alive
   KeepAlive On
   MaxKeepAliveRequests 100
   KeepAliveTimeout 5

   This allows one process to handle multiple sequential requests.
2. Reduce Concurrent Requests: Use lazy loading for images so the browser does not request 20 images simultaneously.
3. Optimize Search Engine Bots: Set the crawl-delay in your robots.txt file:
   

   User-agent: *
   Crawl-delay: 10

   This reduces Google's crawling speed.
4. Use a Queue for Heavy Tasks: Queue long processes (like bulk email sending) using tools like Redis Queue.

Troubleshooting Tip: In cPanel, check the "Entry Processes" section under "Resource Usage". If the Entry Process number is consistently close to the limit, you should either increase the limit or upgrade the site to a VPS.

I/O Limit: The Hidden Bottleneck of Hosting

What Does I/O Limit Mean?

I/O (Input/Output) measures the speed of reading and writing to the hard disk (HDD or SSD). Every operation, such as saving a file, reading the database, or writing logs, consumes I/O. I/O limits are usually defined in terms of IOPS (Input/Output Operations Per Second) or transfer speed (MB/s).

Common Errors Caused by I/O Limits

• Severe Slowness When Uploading Files or installing plugins.
• "Disk quota exceeded" Error even when there is enough disk space.
• Sudden Cron Job Stoppage or failure of scheduled tasks to execute.

How to Reduce I/O Usage

1. Reduce Logging: In WordPress, disable logging plugins. Limit PHP logs by setting error_reporting(0) in your wp-config.php file.
2. Optimize the Database: Convert MyISAM tables to InnoDB (InnoDB has better I/O performance). Use the OPTIMIZE TABLE command weekly.
3. Move Temporary Files to RAM: If your hosting allows, move the /tmp directory to a RAM disk. This can reduce disk I/O by up to 90%.
4. Reduce the Number of Files: Avoid plugins that create thousands of small files (such as some advanced caching plugins). Each small file requires a separate I/O operation.

Common Mistake: Some users enable file caching on disk to fix I/O slowness. This has the opposite effect and increases I/O. Caching should be stored in RAM (e.g., Redis or Memcached).

How to Manage Hosting Resource Limits Overall

To comprehensively manage hosting resource limits, follow these three steps:

1. Continuous Monitoring: Use free tools like htop (via SSH) or WordPress monitoring plugins (like WP Server Stats). Check CPU, RAM, and I/O usage daily.
2. Code Optimization: If your site has custom code, ask a developer to eliminate N+1 queries. One bad query can consume 100% of the CPU.
3. Smart Upgrading: If you still face limits after optimization, instead of buying more expensive hosting, first migrate to a VPS with dedicated resources. ServerNet also offers hosting and VPS services with transparent resources, which can be a suitable option for high-traffic sites.

Remember: no optimization can replace sufficient resources, but with proper management, you can handle up to 3 times more traffic with the same hosting resources.