• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Question How to identify sites causing high load?

martin.g

New Pleskian
Server operating system version
CentOS Linux 7.9.2009 (Core)
Plesk version and microupdate number
Plesk Obsidian Version 18.0.52 Update #3
Hi,

we have a plesk instance with about 80 or 100 websites on it. Although high cpu usage websites are fast responsive, server is not "overloaded". Today I upgraded from 6 to 8 cores and could also put more cores into it. But it would be nice to know which website causes how much load or cpu usage. Thinking about introducing cgroups but I would like to have some stats before.
1685615408144.png

Cheers
Martin
 
There are a couple of ways to identify the issues:

- Use the glances command (available in the Epel repo) and sort on CPU
- Identify which bots are accessing the sites and try to block them:
Code:
# grep -i  bot /var/www/vhosts/*/logs/proxy_access_ssl_log | grep -vE 'bingbot|Googlebot|applebot'

- Monitor the website logs for a while and see which one might be causing the issue:
Code:
# tail -f /var/www/vhosts/system/*/logs/proxy_access_ssl_log
# tail -f /var/www/vhosts/system/*/logs/proxy_error_log
# tail -f /var/www/vhosts/*/logs/error_log
 
Back
Top