At 04:14 PM 3/31/2006, Chris Kantarjiev wrote:
> Are your logs and data on the same partition? That's a bad idea for
> recovering from a blown part of the disk, but we also saw that one of
> our databases would crash when there were lots of
> inserts/updates/replaces -- other databases, which had the same
> version of MySQL and operating system, had the logs and data on a
> separate partition, and they did not crash.
It's a MyISAM table. Are there separate logs files? If so, where?
I thought it was just .frm, .MYI and .MYD. We have MYI and MYD on
separate drives.
We're investigating a possible MERGE organization. I'll report
back if we learn anything new.
Thanks,
chris
Chris,
The problem with Load Data is the larger the table, the slower it
gets because it has to keep updating the index during the loading process.
If you use Load Data on an empty table is will be considerably faster
because the indexes are built after all the data has been loaded. You could
try removing the unique/primary index from the table you are using Load
Data on just as a test to see if it speeds up. Also you can break the Load
Data up into smaller number of rows, say files of 1000 rows each and try that.
Mike
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
