The best way to speed up restores is to not use mysqldump at all. Instead take a snapshot of the filesystem with something like mylvmbackup. Then restore is as fast as copying the files over.
Also mysqldump adds disable keys and disable unique checks to the output by default when using the --opt flag. -Eric On 5/20/07, Ray Cauchi <[EMAIL PROTECTED]> wrote:
Have you tried using the > use db > source /path/to/dumpfile.sql command via the mysql command line client? >At 08:28 AM 5/20/2007, Vitaliy Okulov wrote: >>Здравствуйте, mysql. >> >>How i can speedup restore of mysql DB from file created by mysqldump? > >MySQL is quite fast at reloading data, but if >you don't have enough memory or if >key_buffer_size is not set high enough, then it >can take days to re-index the data. You need to >stuff as much RAM as possible in your machine >and set key_buffer_size to at least 30% of your >machine RAM. I've had indexed take 2+ days to >rebuild and adding more RAM and tweaking >key_buffer_size allowed the same keys to be rebuilt in under an hour. > >Mike -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
-- Eric Bergen [EMAIL PROTECTED] http://www.provenscaling.com
