One thing you could do, which may not be the best, is insert one (or
some set limit) of rows at a time, then after each sleep for .25 seconds
or something, so that your inserts get spread out more over time, and
there is idle time between them for the selecting clients to complete.
Obviously this
Daniel, also consider selecting as high priority. That will cause
select queries to jump ahead of pending insert queries. That will allow
each select to only have to wait for at most one insert to complete.
Cheers,
-Dana
-Original Message-
From: Daniel Cummings [mailto:[EMAIL
From: Simon Ashby [mailto:[EMAIL PROTECTED]]
Sent: 01 July 2002 10:58
To: MYSQL
Subject: Speed issue
Any pointers on how to get rid of the disk churning and get a normal
response in this set up would be much appreciated.
Turn off OBDC logging.
Tim Ward
Brett Ward Limited -
Simon,
Several issues come to mind.
First, as Tim suggested, make sure ODBC logging is turned off. It should be
by default but if you turn it on, it will whip your HD like a bad puppy.
Second, run MySQL on a different machine. More importantly, understand the
difference between Access and
So it may seem that on your machine, with both MySQL and Access loaded
together Access runs ever so much faster. However, you are comparing single
use Access to single use MySQL. (also, once mysql starts caching things, it
gets faster. The more you use it, the faster it runs!) Also, once you
