Let me tell you that we host your cPanel shared hosting account on CloudlinuxOS at Accuwebhosting.com. It allows monitoring the account resource usage that helps to improve server stability and performance.
In cPanel, you can view problematic processes and database queries that are running on your account. It allows you to know what is the reason for exceeding the resource limit.
How to view resource limit information on cPanel?
- Log in to your cPanel. Please refer on how to log in to cPanel?
- Click on the Resource Usage inside METRICS.
- Once you are at the Resource Usage page, you will see cPanel shows you the summary of your account with the below details depending on your cPanel account's resource usage.
- Your site had no issues in the past 24 hours: You will receive this message if your account didn't trigger any limits for the last 24 hours.
- Your site has been limited within the past 24 hours: It means that cPanel account triggered at least one resource limit within the past 24 hours. cPanel also displays the resource with additional information that triggered the limit.
- Your site might hit resource limits soon: You can consider this message as a warning that your account may trigger resource limiting soon.cPanel also displays the resource with additional information that triggered the limit.
- You can view details of resource usage of the cPanel account from the Current Usage tab. You will see a graph-based usage and usage table.
- Generally, cPanel shows the resource usage for the same day. You can change the time from the Timeframe button. Select the time as per your requirement. Using the Time Unit button, you can get the data between the selected time. It could be the day, hour or minute.
- cPanel displays the list of processes and database queries in the snapshot tab. You can use the calendar to get the snapshot between two days.
How does the snapshot helpful to troubleshoot CPU resources limit?
Suppose a cPanel account resource monitor dashboard suggesting that CPU resource is limited for the past 24 hours. To view more information on this, you will need to click on the snapshot.
In the snapshot tab, you will find the below four details.
- Process list: The process list provides a snapshot of the processes currently running on your server. It helps you identify resource-intensive processes, troubleshoot performance issues, and monitor server activity.
- Database Queries: The database queries section shows the currently running database queries. This information can be useful for identifying performance bottlenecks or potential issues with your database applications.
- HTTP Queries: The HTTP queries section displays the currently active HTTP requests. This information can be helpful for debugging web applications or identifying potential sources of traffic congestion.
Understanding Process List Information
The process list information includes the following:
-
PID (Process ID): A unique identifier for each process.
-
User: The user account under which the process is running.
-
Priority: The priority level of the process, which determines how much CPU time it receives.
-
CPU Time: The total amount of CPU time the process has used.
-
Memory Usage: The amount of memory the process is currently using.
-
Command: The name of the command that started the process.
-
Status: The current state of the process, such as running, sleeping, or waiting.
Using Process List Information
You can use the process list information to identify and troubleshoot problems with your server. For example, you can:
-
Identify resource-intensive processes that may be slowing down your server.
-
Track down the cause of performance bottlenecks.
-
Monitor server activity to identify potential security threats.
-
Debug web applications or identify potential sources of traffic congestion.
In general, the process list is a valuable tool for understanding and managing your server's workload. By regularly monitoring the process list, you can identify and resolve potential problems before they affect your users.
Using this information, you can find out which process or file uses high CPU usage on your website. You can involve your developer and fix the code of that script.
