Heikki Tuuri schrieb:
Creating the indexes after the import will only slow down the operation.
MySQL recreates the whole table at CREATE INDEX.
That's new to me, but good to know (always this urban legends...).
Does that only apply to InnoDB or to MyISAM too?
Regards,
A.
--
MySQL General
Andreas,
- Original Message -
From: Andreas Ahlenstorf [EMAIL PROTECTED]
Newsgroups: mailing.database.myodbc
Sent: Friday, March 18, 2005 11:47 AM
Subject: Re: Problem: Slow LOAD FILE performance with innodb
Heikki Tuuri schrieb:
Creating the indexes after the import will only slow down
Hi list,
I'm trying to import some data into a MySQL database. The data-file is
5.5G, and consist of about 132 million rows. The machine is a P4 3GHz
with 1G RAM and a single 250 GB ATA-disk for data. The operating system
is Debian GNU Linux testing with kernel 2.6.8 with hyperthreading
support.
My first guess is the indexes. Maybe create them after the import. It will
nonetheless take a bit of time!
--Original Message--
From: Jarle Aase
To: MySQL list
Sent: Mar 17, 2005 11:53 PM
Subject: Problem: Slow LOAD FILE performance with innodb
Hi list,
I'm trying to import some data
Jarle Aase schrieb:
Is there a way to boost the performance? The database is idle, and while
importing, performance is the key priority (record-locking,
transaction-rollbacks and file-integrety/crash-recovery are not required
until the data are imported).
- Disable the foreign key checks
: Re: Problem: Slow LOAD FILE performance with innodb
My first guess is the indexes. Maybe create them after the import. It will
nonetheless take a bit of time!
--Original Message--
From: Jarle Aase
To: MySQL list
Sent: Mar 17, 2005 11:53 PM
Subject: Problem: Slow LOAD FILE performance
