Answer the question
In order to leave comments, you need to log in
MySQL performance drop during database restore?
There is a server on Debian 7.0 with Mysql 5.6.14. The problem is that when restoring a large database (50 GB) from a neighboring machine, the load on the disk subsystem gradually appears, performance decreases, and the processor is not loaded at 100%.
I also tried to change the file system (for experimental purposes) from EXT4 to EXT3, while the write performance increases, but slightly (!).
RAID10 of 4 SATA drives (hardware).
Restoring two such databases in two threads puts the server tightly, the write speed drops to a couple of megabytes per second.
There is no question in SELECT optimization.
It is interesting to hear advice on the optimal settings for Mysql and OS.
Answer the question
In order to leave comments, you need to log in
Go to mysql and see show processlist;
it will show in what state you have a stupor.
Well, good old iotop
, so if you have large indexes, mysql should build them from scratch when restoring.
And if you try to turn off all indexes and foreign keys for the recovery period, and then turn them on one at a time (starting with indexes)?
Tell me, when you dumped this, did you carefully read man about all sorts of mysqldump options?
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question