When one or more limits of your hosting plan are reached, you will have the option to show a detailed list on the Resource Usage page in hPanel. Just scroll down to find More Details and click on it. The list will contain the following:
The exact time when the limit was hit
CPU usage at that moment
Memory usage at that moment
The exact process that caused the limit to be met
This is useful information for troubleshooting or optimizing your website.
Most Common Cases for Hitting Limits
This process is related to the File Manager, where operations like archiving can cause it to slow down. If you are experiencing any issues with the File Manager, you can try performing actions using an FTP client instead. Another option is to stop the processes by clicking on the banner at the bottom of the Resource Usage section on our panel:
lsphp (Litespeed PHP) is the process responsible for dealing with all of the PHP files required to serve the content to your website visitors. When this process hits limits, it can appear either by itself or in relation to a specific file:
wp-admin.php or admin-ajax.php – this is usually an indicator of too many plugins for your current plan. You can try disabling the plugins and see if the issue can be narrowed down to a single plugin. If the issue persists, try reducing the load on your WordPress website
wp-cron.php – this process is executed on every page load, as WordPress checks if certain actions need to be run. A better approach is disabling wp-cron and using the Cronjobs function on hPanel
High CPU usage with many lsphp processes – this can indicate a DDoS attack or just a sudden surge of visitors. It means that the website is not serving visitors fast enough, and process count increases or cumulative CPU usage hits limits. To fix it, you can try optimizing your website or using a content delivery network.
High CPU and memory usage with few processes – this usually indicates the need to optimize your website, as only a few visitors are generating excessive CPU usage
The most common reasons for mysqld limit to be hit are:
Missing database indexes
Several resource-intensive JOIN operations
All of these can cause your MySQL query to create large temporary tables, which can take up memory, increase the processing time, slow down, or even lose connection to the database server. To solve this, we recommend using our Repair database option.
For WordPress websites, you can use a database optimization plugin such as Advanced Database Cleaner. This will delete any unused tables left from previous plugin installs so they won’t use resources.
In addition, you can build an index and look for any queries that take several seconds or have a high memory usage.
If you have optimized your website and the limits are still being hit consistently, it may indicate that your website has grown and needs more resources to handle all its concurrent visits. In that case, you can consider upgrading your hosting plan to increase all the resources 😊