#SUGGESTION #1 No need to run unique_checks = 0 and foreign_key_checks = 0. See my 3-year-old post Speeding up mysqldump / reload (ASPECT #2 shows a standard header of a mysqldump. Lines 13 and 14 handle the disabling of those checks for you)

#SUGGESTION #2 Please note the InnoDB Architecture (Picture From Percona CTO Vadim Tkachenko)

If you want to reload a MySQL Instance you should temporarily disable the Double Write Buffer.

###STEP #1

Login to the Target Server and run

SET GLOBAL innodb_fast_shutdown = 0; 

###STEP #2

Restart mysqld by setting to innodb_doublewrite to OFF

service mysql restart --innodb-doublewrite=OFF --innodb-fast-shutdown=0 

###STEP #3

Load the mysqldump into the Target Server

###STEP #4

Restart mysqld normally (Double Write buffer will be enabled again)

service mysql restart 

Since the name "Double Write Buffer" implies two writes, InnoDB will only write data and indexes straight to the table files and bypass writing to the Double Write Buffer within ibdata1. Maybe this will double the import time (pun intended)

#SUGGESTION #3

The default innodb_log_buffer_size is 8M. You need a bigger Log Buffer.

Please add this line to my.cnf under the [mysqld] group header

[mysqld] innodb_log_buffer_size = 128M 

Then, restart mysqld before the reload of the mysqldump.

#GIVE IT A TRY !!!

#SUGGESTION #1 No need to run unique_checks = 0 and foreign_key_checks = 0. See my 3-year-old post Speeding up mysqldump / reload (ASPECT #2 shows a standard header of a mysqldump. Lines 13 and 14 handle the disabling of those checks for you)

#SUGGESTION #2 Please note the InnoDB Architecture (Picture From Percona CTO Vadim Tkachenko)

If you want to reload a MySQL Instance you should temporarily disable the Double Write Buffer.

###STEP #1

Login to the Target Server and run

SET GLOBAL innodb_fast_shutdown = 0; 

###STEP #2

Restart mysqld by setting to innodb_doublewrite to OFF

service mysql restart --innodb-doublewrite=OFF --innodb-fast-shutdown=0 

###STEP #3

Load the mysqldump into the Target Server

###STEP #4

Restart mysqld normally (Double Write buffer will be enabled again)

service mysql restart 

Since the name "Double Write Buffer" implies two writes, InnoDB will only write data and indexes straight to the table files and bypass writing to the Double Write Buffer within ibdata1. Maybe this will double the import time (pun intended)

#SUGGESTION #3

The default innodb_log_buffer_size is 8M. You need a bigger Log Buffer.

Please add this line to my.cnf under the [mysqld] group header

[mysqld] innodb_log_buffer_size = 128M 

Then, restart mysqld before the reload of the mysqldump.

#GIVE IT A TRY !!!

#SUGGESTION #1 No need to run unique_checks = 0 and foreign_key_checks = 0. See my 3-year-old post Speeding up mysqldump / reload (ASPECT #2 shows a standard header of a mysqldump. Lines 13 and 14 handle the disabling of those checks for you)

#SUGGESTION #2 Please note the InnoDB Architecture (Picture From Percona CTO Vadim Tkachenko)

If you want to reload a MySQL Instance you should temporarily disable the Double Write Buffer.

###STEP #1

Login to the Target Server and run

SET GLOBAL innodb_fast_shutdown = 0; 

###STEP #2

Restart mysqld by setting to innodb_doublewrite to OFF

service mysql restart --innodb-doublewrite=OFF 

###STEP #3

Load the mysqldump into the Target Server

###STEP #4

Restart mysqld normally (Double Write buffer will be enabled again)

service mysql restart 

Since the name "Double Write Buffer" implies two writes, InnoDB will only write data and indexes straight to the table files and bypass writing to the Double Write Buffer within ibdata1. Maybe this will double the import time (pun intended)

#SUGGESTION #3

The default innodb_log_buffer_size is 8M. You need a bigger Log Buffer.

Please add this line to my.cnf under the [mysqld] group header

[mysqld] innodb_log_buffer_size = 128M 

Then, restart mysqld before the reload of the mysqldump.

#GIVE IT A TRY !!!

#SUGGESTION #1 No need to run unique_checks = 0 and foreign_key_checks = 0. See my 3-year-old post Speeding up mysqldump / reload (ASPECT #2 shows a standard header of a mysqldump. Lines 13 and 14 handle the disabling of those checks for you)

#SUGGESTION #2 Please note the InnoDB Architecture (Picture From Percona CTO Vadim Tkachenko)

If you want to reload a MySQL Instance you should temporarily disable the Double Write Buffer.

###STEP #1

Login to the Target Server and run

SET GLOBAL innodb_fast_shutdown = 0; 

###STEP #2

Restart mysqld by setting to innodb_doublewrite to OFF

service mysql restart --innodb-doublewrite=OFF --innodb-fast-shutdown=0 

###STEP #3

Load the mysqldump into the Target Server

###STEP #4

Restart mysqld normally (Double Write buffer will be enabled again)

service mysql restart 

Since the name "Double Write Buffer" implies two writes, InnoDB will only write data and indexes straight to the table files and bypass writing to the Double Write Buffer within ibdata1. Maybe this will double the import time (pun intended)

#SUGGESTION #3

The default innodb_log_buffer_size is 8M. You need a bigger Log Buffer.

Please add this line to my.cnf under the [mysqld] group header

[mysqld] innodb_log_buffer_size = 128M 

Then, restart mysqld before the reload of the mysqldump.

#GIVE IT A TRY !!!