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

Mysqldump performance degradition

mavera2

Basic Pleskian
Inside my cronjobs I make a full mysqldump every night.
My database has total 1.5GB data inside 20 tables.
Nearly every table has indexes.

I make backup like this:

mysqldump --user=user--password=pass--default-character-set=utf8 database| gzip > "$mybackupfile"

I make this for 2 months. This process takes nearly 1,5 minutes for 2 months.

Last week my hosting company changed my server. Just after the server change, this process started to long for 5 minutes. I told this to server company and they increased my CPU from 4GHz to 6 GHz so mysqldump process became 3,5 minutes. Then they increased to 12 GHz. But this didn't change the performance.

I checked my shared SSD disk performance with `hdparm`. It was 70 MB/sec. So I complain again. So they changed my hard disk to another one. Hard disk read speed became 170 MB/sec. So mysqldump process became 3 minutes.

But the duration is far from the previous value. What would be the cause for this performance degradion ? How can I isolate the problem ?

(Server is Plesk 11.5, Centos 6.4, 12 GHz CPU, 8 GB RAM)
 
Back
Top