Brent Baisley wrote:
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.
This customer regularly request new things, so I cannot avoid changes
to the database structure.
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.
I found in the MySQL documentation that the row-level locking of InnoDB
is slower if you need to do frequent full table scans. Unfortunately, I
can not avoid them (3rd party application running there).
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.
OK, thanks.
How about DELAY_KEY_WRITE=1 ? Does this speed up things substantially ?
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]
