Changes to the database structure should be few a far between. If you are finding you need to change the structure regularly, you
should probably look at a redesign.
MyISAM locks the table when an insert/delete is occurring, during which time other requests are queue up. You can switch it to
InnoDB, which does not use table locking. This can be done easy enough with an Alter table command, but make sure you read up on
what InnoDB doesn't support (full text searching). InnoDB does take up a lot more space than MyISAM, so make sure your file system
supports files over 2GB.
If you need to stick with MyISAM, you may want to change the way you do inserts/deletes, breaking them up into chunks. Then you'll
be "interleaving" you insert/deletes with other requests.
----- Original Message -----
From: "Stefan Hornburg" <[EMAIL PROTECTED]>
To: <mysql@lists.mysql.com>
Sent: Tuesday, July 11, 2006 8:52 AM
Subject: Speedup of database changes
Hello,
one of my customers has a database with about 1.7 million records
(52 fields, almost 1GB on amd64, MyISAM).
This database is running on Debian sarge with MySQL 4.0.24.
Changing the database structures and also large set of inserts/deletes
take too long to be acceptable on a productions system.
What can I do to speedup these operations ?
Bye
Racke
--
LinuXia Systems => http://www.linuxia.de/
Expert Interchange Consulting and System Administration
ICDEVGROUP => http://www.icdevgroup.org/
Interchange Development Team
--
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]
