Import through MySQL - exported on master: 1.808s The settings in the most recent version of PMA seem to produce a file that is almost as optimized as the one from mysqldump. The optimized SQL from mysqldump doesn't use transactions but it has only 9 INSERTs per table. There are 181 INSERTs for table sbtest1 which means that the data is committed 181 times. I don't know about the settings in version 4.4.15.10 but it seems to have produced a file without START TRANSACTION which is definitely a huge bottleneck. The mysqldump command by default uses -opt option which produces a file that can be imported much quicker. On top of that, the default settings for export in PMA produce suboptimal SQL file. Then for every single query from the file, it has to send it to the server. It has to parse the file and split it up into separate queries. The truth is that phpMyAdmin is not the best tool to load medium/large SQL files.
I started to analyse this as it's an interesting topic, but so far I don't see any opportunity to optimize this.
0 kommentar(er)
