• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

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