[GLLUG] crossloading a mysql db - improvements to shell script?

tid td at bloogaloo.co.uk
Mon Apr 7 08:25:53 UTC 2014


Hi Folks,

I'm seeking to improve a database crossload from one mysql server to
another and am looking for any ideas / suggestions.

Previously, the client was using :

-------------------------------------------------
dump fromserver db1 > file1.sql
dump fromserver db2 > file2.sql
cat file1 | mysql toserver db1
cat file2 | mysql toserver db2
-------------------------------------------------

which I've speeded ( sped?) up by

-------------------------------------------------
dump fromserver db1 > file1.sql &
dump fromserver db2 > file2.sql &
wait
cat file1 | mysql toserver db1 &
cat file2 | mysql toserver db2 &
wait
-------------------------------------------------

I can obviously do this:

dump fromserver db1 | mysql toserver db1

at which point the network becomes the bottleneck. Is it possible to
improve performance by bonding network interfaces? The only fly in the
ointment here is that the mysql server is an AWS RDS instance, and
therefore I can't add interfaces to it - only to the server where my script
runs.

Any thoughts / suggestions / guffahs of laughter gratefully received.

Cheers,

Tid
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.lug.org.uk/pipermail/gllug/attachments/20140407/4a45c34c/attachment.html>


More information about the GLLUG mailing list