in reply to Optimizing mysql and inserts
I regularly run scripts to rebuild MySQL tables from scratch and reload them with data records. A quick line count tells me about 1.2 million text records in various combinations of insert/delete/update. The text records are parsed, and submitted as MySQL requests by Perl, one by one through DBI connection without the benefit of prepared statements. It takes roughly 10 minutes to completely process. This is running on my desktop box, nothing fancy. So unless you have a seriously under powered computer (I doubt it) or a network storage limitation or database locking issues, I doubt that MySQL is your bottleneck.
You need to find out where the code is spending it's time. A few well placed print statements should point you in the right direction fairly quickly.
|
---|
Replies are listed 'Best First'. | |
---|---|
Re^2: Optimizing mysql and inserts
by gossamer (Sexton) on Jul 11, 2012 at 19:51 UTC | |
by huck (Prior) on Mar 15, 2017 at 02:47 UTC | |
by ruzam (Curate) on Jul 11, 2012 at 22:10 UTC |