Re: 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.

Comment on Re: Optimizing mysql and inserts

Replies are listed 'Best First'.
Re^2: Optimizing mysql and inserts by gossamer (Sexton) on Jul 11, 2012 at 19:51 UTC
I've commented out the "$dbh->do($sql);" in my code, and it's substantially faster. That is definitely the bottleneck. ...few minutes later, after a few trial runs... I grabbed a my.cnf from a larger server and put it in place of the existing one, and it's magnitudes faster! Turns out it was in how mysql was configured. I think it's much better now. I'm actually pretty proud of myself for this, and thanks for everyone's help as well! Thanks, Alex	[reply]
Re^3: Optimizing mysql and inserts by huck (Prior) on Mar 15, 2017 at 02:47 UTC
I am surprised nobody ever mentioned `$rc = $dbh->begin_work; $rc = $dbh->commit;` [download] http://search.cpan.org/~timb/DBI-1.636/DBI.pm#commit Any time you work with more than a tiny few records you want to use begin_work and commit yea i know its old, and you probably know this by now	[reply] [d/l]
Re^3: Optimizing mysql and inserts by ruzam (Curate) on Jul 11, 2012 at 22:10 UTC
Not that it's Perl related, but what kind of differences did you find in the my.cnf file?	[reply]


Perl-Sensitive Sunglasses
	PerlMonks