Whenever you reach some of your hosting plan’s limits repeatedly, you will see a notification, similar to this:
This notification lets you know about the issue (hitting limits) in general, but if you want to check detailed statistics, we have just a tool for that!. Detailed list of resource usage lets you know what exactly caused the limit to be hit. It works by generating a list of entries for each time limit was hit in the past 24 hours and can be found just below the Storage performance (IOPS) graph:
The list shows:
The exact time when the limit was hit
CPU usage at that moment
Memory usage at that moment
The exact process which has caused the limit to be hit in the first place
Most common cases
Filebrowser: IOPS, NPROC
In case you are seeing this entry:
It means it's linked to our new File Manager (beta), as it's still in beta version, heavy IO/IOPS operations like archiving can cause it to slow down. If you are experiencing any issues with our new FIle Manager, you can try performing actions via our default File Manager or via FTP client. Another option is to Stop all currently running processes, this option can be found at the bottom of the Order Usage section:
lsphp: All limits
lsphp is a process responsible for how the Litespeed web server serves your webpage to your visitors. It basically processes all of the PHP files to serve the generated content to visitors.
For example, big CMS applications like WordPress can have many plugins, many of which are not optimized that well. For this reason, you can see such entries in detailed list of resource usage:
CPU or IO when accessing wp-admin - usually an indicator of too many plugins for your current plan or lack of optimization. A good idea is to try to disable a few and see if the issue can be narrowed down to a single plugin
CPU or IO when accessing wp-cron - wp-cron is run on every page load, as WordPress checks if certain actions need to be run. A better approach is disabling wp-cron and using our Cronjobs on hPanel
NPROC or CPU with many lsphp processes - this can indicate a DDOS attack or just a sudden surge of visitors. Basically, the website does not serve visitors fast enough, and process count increases or cumulative CPU usage hits limits. Optimization, an upgrade, or CDN like Cloudflare are good solutions here
CPU, IO, Physical memory, with few processes - Usually indicates a lack of website optimization as it causes only a few visitors to generate a lot of CPU usage
mysqld: CPU and Physical memory
The most common reasons for mysqld limit to be hit is:
Missing database indexes
Several expensive JOIN operations
All of these can cause your MySQL query to create large temporary tables which can take up memory of processing time, as a result slowing down or even losing connection to the MySQL server. To solve this, we recommend using our Repair database option in hPanel as it does repair and optimize your database.
For WordPress specifically, we recommend using a database optimization plugin such as Advanced Database Cleaner. This will ensure that any useless tables left from previous plugin installs will be deleted and won’t use your resources.
Lastly, we suggest building an index and looking for any queries that take several seconds or use a lot of memory.