You have a consistent InnoDB backup created with mysqldump, the largest table is 50 GB in size.
You start to restore your backup with this command;
shell> mysql
–
u root
–
p < backup.sql
After 30 minutes, you notice that the rate of restore seems to have slowed down. No other
processes or external factors are affecting server performance.
Which is the most likely explanation for this slowdown?
您使用mysqldump创建了一致的InnoDB备份,最大的表大小为50GB。您开始使用此命令恢复备份;shell>mysql-uroot-p<backup.sql30分钟后,您会注意到恢复速率似乎已降低。没有其他进程或外部因素会影响服务器的性能。对这种经济放缓最有可能的解释是什么?
A. The MySQL server has stopped inserting data to check index consistency.
B. InnoDB is doing CRC32 checks over the tablespace data as it grows.
C. The MySQL server is taking a periodical snapshot of data so it can resume the restore if it is
interrupted mid-way.
D. InnoDB has filled the redo log and now must flush the pages.
E. Secondary indexes no longer fit into the buffer pool.
A. MySQL服务器已停止插入数据以检查索引的一致性。
B.InnoDB正在执行CRC32对表空间数据进行检查。
C.MySQL服务器正在定期拍摄数据快照,以便在中途中断时可以恢复恢复操作。
D.InnoDB已填充了重做日志,现在必须刷新页面。
E.辅助索引不再适合于缓冲池中