You could try changing the priority of your inserts using INSERT LOW PRIORITY
See: http://www.mysql.com/doc/en/INSERT.html
This will give the selects priority over the inserts, as the table becomes
free, the insert will happen.
Also, look at this:
http://www.mysql.com/doc/en/Insert_speed.html
-J
-----Original Message-----
From: Seth Brundle [mailto:brundlefly76@stripped]
Sent: Wednesday, February 26, 2003 2:01 PM
To: mysql@stripped
Subject: copying databases to avoid insert holdups
I have a MySQL database I will be launching soon which has a search engine
database accesable over DBI/mod_perl/Apace. It has about 2M records, and is
a 4GB table with 1GB index.
Every day I insert 76k records all at once and delete about another 76k.
While these inserts are happening, the select performance is obviously
impacted.
What I want to do is to have two copies of the database, copying the updated
version to the publicly-accessable one, i.e.:
mysql stop
rm -rf /mysql/data/publicdbdir
copy -r mysql/data//insertdbdir mysql/data/publicdbdir
mysql start
My question is this:
Is this enough to prevent me from experiencing slow inserts and queries
during insert, or should I be firing up two seperate servers?
Also - if I create the MyISM tables on 3.23, can copy them to a 4.0.10
server's data directory? (the reason i ask is that I have a 3.23 server
available on that box)
Thanks
q
---------------------------------------------------------------------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail <mysql-thread133470@stripped>
To unsubscribe, e-mail <mysql-unsubscribe-jtinley=unirez.com@stripped>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
