2.26.1. Server resource consumption graphs

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

Buttons under the charts:

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

Exceeding the available limits may have various consequences.

The graph of the load on the central processing unit (CPU) for the last 24 hours:

• "Maximum " — maximum load on the CPU.
• "Average " — average load on the CPU.

A single core load percentage of 100 means that 1 core is used at 100%, 200 is used for 2 cores, and so on.

RAM consumption graph for the last 24 hours:

• Shared hosting
• Business hosting

• "Maximum " — how much maximum memory was used by the web server in 5 minutes.
• "Average " — how much memory the web server used on average in 5 minutes.
  • Includes memory for additional services (only the volume actually used is taken into account, not the entire allocated volume).
• "Failed" — attempts to use memory by the web server in excess of the available limit.

• "Maximum " — how much maximum memory was used in total by the web server and the MySQL server in 5 minutes.
• "Web server " — how much memory the web server used on average in 5 minutes.
  • Includes memory for additional services (only the volume actually used is taken into account, not the entire allocated volume).
  • The graph displays not from zero, but from the value "MySQL".
• "MySQL" — how much memory the MySQL server used on average in 5 minutes.
• "Cache" — how much conditionally free memory the file system used for cache in 5 minutes.
  • The operating system kernel releases this memory first when it needs to allocate more memory for higher priority services — the web server and the MySQL server.
  • The graph is displayed on top of the rest.
• "Failed" — attempts to use memory by the web server in excess of the available limit.
• "Failed — MySQL" — attempts to use memory by the MySQL server in excess of the available limit.

Consumption schedule cpu minutes for the last week:

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

Graph of the number of processes for the last day:

• "Maximum " — the maximum number of processes.
• "Average " — the average number of processes.
• "Limit " — the limit on the number of processes.
• "Failed" — a value indicating the use of the number of processes in excess of the available limit.

Graph of the number of requests to the Apache and nginx web server for the last 24 hours:

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

Graph of the number of requests to databases for the last month:

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

Graph with statistics of incoming and outgoing mail for the last month:

It is important to take into account that there are restrictions on the consumption of server resources for both shared hosting and businesshosting... But if within the framework of shared hosting there is such a limitation as cpu minute, then within the framework of business hosting there is no such limitation, however, there are still limitations that are due to the provided server resources corresponding to the tariff plan used.

When the graphs of the consumption of CPU and RAM resources show high values, then such consumption can lead to huge problems in the operation of all sites of the hosting account and you should immediately take action to fix the problem.

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

• Slowdown of site scripts and slow page loading.
• The occurrence of errors on the site due to a long wait or the impossibility of performing a particular process.
• The emergence of the multitude errors 503.
• Height number of processes followed by errors 508.

To fix the problem, you can use the recommendations provided in the instructions for elimination of the generated load.