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

[Steve Parker]

If you can't change the throughput of the MySQL server, any other tweaks elsewhere would probably make no difference.  If your client machine has a very slow NIC on an otherwise fast network, you could use NIC bonding to improve your throughput, but the bottleneck is more likely to be between AWS and your client
 
-----Original Message-----
From: "tid" <td at bloogaloo.co.uk>
Sent: Monday, April 7, 2014 9:24am
To: "The mailing list for the Greater London Linux User Group" <gllug at mailman.lug.org.uk>
Subject: [GLLUG] crossloading a mysql db - improvements to shell script?



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/859b8416/attachment.html>