• 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.

mysqld

M

met00

Guest
CPU GenuineIntel, Intel(R) Pentium(R) 4 CPU 3.00GHz
Version psa v7.5.4_build75060617.18 os_FedoraCore 3
OS Linux 2.6.11.9-050512a

###

mysqld seems to run away with all the CPU. starts out taking chunks at 20%-30% for 3-5 refreshes of "top", then drops out for 2-3 refreshes, then bounces back up. Server is running very few active processes (httpd's) as it's 3 in the morning.

This is AFTER we saw it at 99% (uptime was 63 days) and it was at 99% of the CPU and not dropping, ever.

any suggestions on where to even start looking for why mysqld seems to run away and eat up massive amounts of CPU. Thanks in advance.
 
You may want to watch threads_created status variable. If there is a lot of threads being created and/or destroyed then you will find mysql is spending a high % of sys CPU time.

mysqladmin extended-status |grep -i threads_created/quote]

If it is creating and destroying alot of threads then you should tune the thread_cache_size variable in /etc/my.cnf:

set-variable = thread_cache_size=32

If it is user CPU time, then you may want to take a look at the slow queries. You can enable logging of slow queries by tweaking /etc/my.cnf:

set-variable = long_query_time=4
log-slow-queries=/var/lib/mysql/slow.log

You may want to take a peek at mytop and mysqlreport:

mytop
mysqlreport

They are both good tools for tuning mysql.
 
Back
Top