Resource Overused - Wordpress Plesk Hosting

To view the resources usage for your website, kindly log into your Wordpress admin dashboard from Exabytes Client Area.

Resource available for checking:    

  • CPU Usage

  • Physical Memory Usage

  • Entry Processes

  • Number of Processes      

  • IOPS

  • I/O Usage

  • Virtual Memory

CPU Usage : 100%

CPU Usage is one of the indicator for speed of loading for website. 

Hitting CPU Usage 100% will cause your site to slow down until CPU Usage is below 100%. 

No error will be displayed for hitting CPU Usage limit. 

Physical Memory Usage : 2.0G

Physical Memory depends on the package you subscribed. 

508 Resource Limit Reached” or “500 Internal Server Error”  may be displayed for hitting Physical Memory Usage limit.

Entry Processes : 20

Entry Processes is the number of concurrent Apache connections a website can sustain. 

The word 'concurrent' refers to processes happening at the same time. 

You could have hundreds and thousands of connections but having all connections performing tasks simultaneously is unlikely. 

Hitting this limit generally hints that the site is getting hit hard by bots and crawlers. 

503 Service Temporarily Unavailable” will be displayed for hitting Entry Processes.

Number of Processes : 100

Number of Processes refers to total number of active processes allowed on a domain. 

Services below are examples of the processes:   

  • HTTPD (website connections)

  • PHP processes

  • SMTP/IMAP/Sendmail

  • Cronjobs     etc

Hitting this limit will require one process to end for the next one to be generated.

Apache 500 or 503 errors will be displayed for hitting Number of Processes limit. 

IOPS : 2048

IOPS refers to Input/Output per second. This resource limits the total number of read or write operations per second. 

This limit does not usually get hit as other resource will be hit before IOPS is hit. If it does hit, it will be queued for the next operation after the current one ends. 

One of the indicator is slow loading of web pages.

I/O Usage : 2048

I/O Usage refers to Input and Output. I/O Usage refers to the work done by drives to read and write data. 

Hitting this limit will cause website to slow down (but still available) until the usage has decreased.  

Steps to check and resolve resource overusage

Step 1    :    Log into Plesk Panel

Log into your Plesk panel via Manage My Wordpress in Exabytes Client Area.

On the left side, click on Websites & Domains.

Click on resource usage at the right side of the page.

A pop up will show for selection of webspace which you would like to view the resource usage. Upon selection, click OK.

Step 2    :    Resource Usage

There are two tabs under Resource Usage (Index and Details). 

Index shows the issues for the past 24 hours.

Details shows the individual resource usage.

Apart from numerical statistics, there are also individual graphs for the resource usage. 

Step 3    :    500 Internal Server Error

Possible Errors

  • "500 Internal Server Error"
  • "HTTP 500"
  • "Internal Server Error"
  • "HTTP 500 - Internal Server Error"
  • "500 Error"
  • "HTTP Error 500"
  • "500 - Internal Server Error"
  • "500 Internal Server Error. Sorry something went wrong."
  • "500. That's an error. There was an error. Please try again later. That's all we know."
  • "The website cannot display the page - HTTP 500."
  • "Is currently unable to handle this request. HTTP ERROR 500."

Step 4    :    Troubleshooting Section

Possible Issues

  • Browser Cache
  • Incorrect database login credentials
  • Corrupted database 
  • Corrupted files in your WordPress installation

  • Issues with your database server
  • Corrupted WordPress core files
  • Corrupted .htaccess file and PHP memory limit
  • Issues with third-party plugins and themes

  • PHP timing out or fatal PHP errors with third-party plugins

  • Wrong file and folder permissions

  • Exhausted PHP memory limit on your server

  • Corrupted or broken .htaccess file

  • Errors in CGI and Perl script

Possible Solutions

  • Try reloading the page
  • Clear your Browser Cache
  • Check your Server Logs
  • Check your Plugins and Themes
  • Reinstall WordPress Core
  • PHP Memory Limit
  • Problem with your .htaccess file 
  • Coding or Syntax Errors in your CGI/Perl Script
  • Update WordPress
  • Use a caching plugin
  • Image Optimization
  • Clean and Optimize Database
  • Disable WordPress Crons
  • Enable CDN
  • Configure WP Disable
  • Enable Opcode cache
  • Limit WordPress crawl rules
  • Limit Google/Bing Crawl rate
  • Install Heartbeat Control function
  • Fix XMLRPC attack
  • Upgrade PHP version

If the above does not resolve the issue, please submit a case to [email protected] (.com/.sg) for further assistance. 


Did you find it helpful? Yes No

Send feedback
Sorry we couldn't be helpful. Help us improve this article with your feedback.