Mitch Pirtle wrote:
Um, I can outdo that on my Dell laptop. ?
Hey, (snaps fingers) I got an idea, maybe you can bring in a specialist to performance tune? (evil grin)
Seriously, something has to be really wrong here, because a "basic" table (say, 20 columns, mixed int/char/varchar) with 20,000 records in an insert with mysqlimport should go in minutes, not hours. The only time I've seen something like that (beyond Access) was an Oracle database with a perl load script (no commits, the whole durn thang) and eensy-weensy rollback segments that got splattered to smithereens. But with MySQL I was loading imports of >100,000 records in less than an hour on a dual P-III 333 MHz machine, with the world's slowest RAID controller[TM].
If you want, I can maybe ask a few questions to find out what the problem is, but that's off-topic. Seems like somebody forgot to put some oil in that Ferrari -;^>=
Well, it sounds like someone put a rusty old tractor engine under the hood! As I said before, it's not something I'm directly involved in, so I have no idea about any implementation issues. I just see it getting slower as more records are added. Retrieving the data hasn't showed any problems though.