2.17.3. Server resources consumption charts

Charts are displayed at the bottom of the "Hosting" section.

Buttons below the charts:

• "Customize charts" — enable/disable required charts and change their order.
• "Update charts" — update information on all charts.

Exceeding the available limits can have various consequences.

CPU load chart for the last 7 days:

• "Limit" — CPU load limit (at low load may not be visible on the chart).
• "Maximum" — maximum CPU load.
• "Average" — average CPU load.

A single core utilization percentage of 100 means 1 core is 100% utilized, 200 means 2 cores, and so on.

RAM usage chart for the last 7 days:

• Shared hosting
• Business hosting

• "Maximum" — how much maximum memory the web server used in 5 minutes.
• "Average" — how much memory the web server used on average in 5 minutes.
  • Includes memory for extra services (only the actual used capacity is counted, not the entire allocated capacity).
• "Failed" — attempts to use memory by the web server over the available limit.

• "Maximum" — how much maximum memory the web server and MySQL-server used in 5 minutes.
• "Web server" — how much memory the web server used on average in 5 minutes.
  • Includes memory for extra services (only the actual used capacity is counted, not the entire allocated capacity).
  • The chart does not display from zero, but from the value "MySQL".
• "MySQL" — how much memory the MySQL server used on average in 5 minutes.
• "Failed" — attempts to use memory by the web server over the available limit.
• "Failed — MySQL" — attempts to use memory by MySQL server over the available limit.

Exceeding the limit usually causes 503 errors.

Chart of the number of entry processes (PHP scripts, cron jobs, and SSH sessions running at any given moment) for the last 7 days:

• "Limit" — limit of the number of processes (if the number of processes is small, it may not be visible on the chart).
• "Maximum" — maximum number of processes.
• "Average" — average number of processes.
• "Failed" — number of processes over the available limit.

Exceeding the limit usually causes 508 errors. Common reasons: active work of scripts, high traffic (real visitors, active indexing by search engines, requests from bad bots, DDoS attack), many loaded sites in the hosting account, sites using too many plugins, poorly written scripts, etc.

Chart of CPU minutes consumption for the last month:

• "Web" — web server:
  • "overage" — consumption of CPU minutes in excess of the norm (more than 100 CPU minutes per day).
  • "normal" — CPU minutes consumption within the normal range (up to 100 CPU minutes per day).
• "MySQL" — MySQL server:
  • "overage" — consumption of CPU minutes in excess of the norm (more than 100 CPU minutes per day).
  • "normal" — CPU minutes consumption within the normal range (up to 100 CPU minutes per day).

Chart of the number of disk subsystem I/O operations for the last 7 days:

• "Limit" — limit of the number of operations.
• "Maximum" — maximum number of operations.
• "Average" — average number of operations.

Chart of number of requests to Apache and nginx web server and number of requests from Google for the last 24 hours:

The "More" button expands/collapses the list of top 3 sites that create load on the server.

Chart of the number of queries to databases for the last month:

The "More" button expands/collapses the list of the top 3 database users that create load on the server.

Chart is similar to Entry processes, but includes all processes of the hosting account for the last 7 days:

• "Limit" — limit of the number of processes (if the number of processes is small, it may not be visible on the chart).
• "Maximum" — maximum number of processes.
• "Average" — average number of processes.
• "Failed" — number of processes over the available limit.

Exceeding the limit usually causes 500 and 503 errors.

It is important to keep in mind that there are server resource consumption limits for both shared hosting and business hosting. But if shared hosting has such a limitation as CPU minute, then business hosting has no such limitation, but there are still limitations, which are conditioned by the provided server resources corresponding to the plan used.

When the CPU and RAM resource consumption charts show high values, this consumption can lead to problems in the operation of all the sites of the hosting account and it is worthwhile to immediately start looking for ways to fix the problem.

The main problems that can be observed with high resource consumption:

• Slowdown of site scripts and slow loading of pages.
• Errors on the site due to long waiting times or inability to perform a particular process.
• Errors 500 (see Number of processes).
• Errors 503 (see RAM, Number of processes).
• Errors 508 (see Entry processes).

To resolve the problem, you can use the recommendations in the instructions for eliminating the load created.