Harrison Fisk wrote:
There isn't really any way to "use" concurrent INSERT. It happens
automatically if possible. However there are a few things you can do
to help it along, such as OPTIMIZE after you DELETE large portions of
the table. Also it does have to enabled in LOAD DATA INFILE
manual
Hi,
On May 8, 2005, at 1:47 PM, Kevin Burton wrote:
Harrison Fisk wrote:
aren't loaded into the query cache, they are loaded into the key
cache (key_buffer_size).
Yes... you busted me ! :). I meant to say key cache though.
Alright, I assumed a typo or such.
Not only THAT but it doesn't need to rea
Harrison Fisk wrote:
aren't loaded into the query cache, they are loaded into the key cache
(key_buffer_size).
Yes... you busted me ! :). I meant to say key cache though.
Now assuming that you have the query cache actually being used (the
cache of the actual statement), then normally the SELECT
Hi Kevin,
On May 8, 2005, at 1:07 PM, Kevin Burton wrote:
OK.
Lets take a mythical application. The app is spending about 50% of
its time inserting into table FOO. The other 50% of the time its
spent doing SELECT against the table.
The SELECTs can use an index which is already full loaded into
OK.
Lets take a mythical application. The app is spending about 50% of its
time inserting into table FOO. The other 50% of the time its spent
doing SELECT against the table.
The SELECTs can use an index which is already full loaded into the query
cache. Not only THAT but it doesn't need to re
