To provide a fast, stable, and secure hosting environment, Laughing Squid utilizes CloudLinux. This technology creates an isolated environment for your website, providing dedicated server resources (CPU and RAM).
If your website experiences a surge in traffic, runs a heavy background task, or uses a poorly optimized plugin, you may receive an automated email notification that you have hit a "Resource Limit." You might also see your website temporarily slow down or display a "Resource Limit is Reached" error.
Here is a breakdown of what these limits mean and how to investigate them.
The Core Resource Metrics Explained
When you log into your DirectAdmin panel and click on Resource Usage, under the Extras section. You will see several acronyms. Here is what they stand for:
SPEED (CPU Usage): The amount of processing power your site is using.
When you hit this limit, your website will not go offline, but it will temporarily slow down until the heavy task finishes.
Common causes: Heavy WordPress themes, complex database queries, or sudden traffic spikes.
PMEM (Physical Memory / RAM): This is the short-term memory your website uses to process active tasks.
When you hit this limit, visitors may see a 508 or 503 error page until memory frees up.
Common causes: Running too many plugins, WooCommerce cart processing, or poorly coded scripts.
EP (Entry Processes): This is the number of simultaneous PHP scripts your site can process at the exact same millisecond. (Note: This is not the number of concurrent website visitors.)
When you hit this limit, visitors will see a 508 Resource Limit is Reached error.
Common causes: Brute-force bot attacks, default WordPress background tasks (
wp-cron.php), or extremely high traffic on uncached pages.
IO (Input/Output): This measures how quickly your account can read from or write to the server's NVMe SSD storage drive.
When you hit this limit, your website's background tasks will slow down, but the site usually stays online.
Common causes: Large backup plugins compressing files, malware scans, or bulk importing products.
IOPS (Input / Output Operations Per Second): Similar to IO, but measures the number of read/write requests rather than the size of the data.
NPROC (Number of Processes): The total number of all processes running on your account (including PHP, cron jobs, and SSH sessions).
How to Find What is Causing the Issue
You don't have to guess what is slowing down your site. Your DirectAdmin panel takes a "snapshot" of your website exactly when it hits a limit.
Log in to DirectAdmin.
Navigate to Extras -> Resource Usage.
Click on the Snapshots tab.
Select the date and time of the warning.
Look at the CMD (Command) column. This will show you the exact file path or plugin that caused the spike (for example,
/wp-content/plugins/backup-plugin/orwp-cron.php).
How to Fix Resource Limit Issues
Once you know what is causing the spike, you can take action:
Install a Caching Plugin: Using a plugin like LiteSpeed Cache or WP Super Cache serves static pages to visitors, drastically reducing CPU, RAM, and EP usage.
Audit Your Plugins: Remove any plugins you no longer use.
Reschedule Heavy Tasks: Configure backup plugins or security scanners to run during the middle of the night when regular traffic is low.
Manage WP-Cron: If
wp-cron.phpis causing the issue, you can disable it in yourwp-config.phpfile and set it up to run manually every 30 minutes via DirectAdmin Cron Jobs.Upgrade Your Plan: If your site is well-optimized but you are consistently hitting your limits due to high traffic, it's time to upgrade to a higher Cloud Hosting tier to get more dedicated resources.
Comments
0 comments
Article is closed for comments.