• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

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