Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I’m dumping a database into a file (piping the dump through gzip) and it takes about 2 minutes to create a 300MB dump.sql.gz file.
When loading the file back into MySQL (the dump begins with dropping the tables), the load takes around 30 minutes!!
What can be the reason for such a huge difference in times? Are there any general tips for drastically reducing the load times?
Thanks.
One reason is that writing to a database is MUCH more expansive than reading from it. The database has to make sure writes are transactional, it has to update indexes, expand files, and so on.
Another resaon is that MySQL dumps a SQL version of your data, like a ton of
insertstatements in a big text file. That’s very slow. Backups from other databases are usually binary files that can be written over the original database, which is faster than restoring one row at a time.