Hi.
You may want to try a combined index (RecordNumber, WordNumber) on
wordindex, because the indexes you have can only restrict on field
(RecordNumber in the EXPLAIN below) e.g.
ALTER TABLE wordindex ADD UNIQUE(RecordNumber, WordNumber);
I presume that the RecordNumber/WordNumber pairs are uni
g it three times
> -Original Message-
> From: René Tegel [SMTP:[EMAIL PROTECTED]]
> Sent: 06 February 2001 14:35
> To: Tim Samshuijzen; [EMAIL PROTECTED]
> Subject: Re: amazingly slow
>
> Tim,
>
> Hmmm... so you are suggesting the format of the query mig
s over time they lose their performance enhancement.
>could that be true?
>
>dan
>
>
>-Original Message-
>From: Tim Samshuijzen [mailto:[EMAIL PROTECTED]]
>Sent: Tuesday, 6 February 2001 04:50
>To: [EMAIL PROTECTED]
>Subject: Re: amazingly slow
>
>
>
&g
Tegel" <[EMAIL PROTECTED]>
>Sent: Tuesday, February 06, 2001 3:07 PM
>Subject: Re: amazingly slow
>
>
>
>Yep, all requested fields are indexed.
>
>At 02:25 PM 6-2-2001 +0100, you wrote:
>>Tim,
>>Just kidding about the 513 Mb
>>
>>you put an
?
regards,
rene
- Original Message -
From: "Tim Samshuijzen" <[EMAIL PROTECTED]>
To: "René Tegel" <[EMAIL PROTECTED]>
Sent: Tuesday, February 06, 2001 3:07 PM
Subject: Re: amazingly slow
Yep, all requested fields are indexed.
At 02:25 PM 6-2-2001 +0100, you
50
To: [EMAIL PROTECTED]
Subject: Re: amazingly slow
Dear Dave,
Thanks for your reply.
(The table actually works with word numbers, as the words
are present in a hash table. I explained it the way I did
because functionally it is the same. So the actual search
is for WordNumber values instead of
lt;[EMAIL PROTECTED]> writes:
>
>> This still does not tell me why the query is amazingly slow.
>
>What else is happening on the system? what does, say, a vmstat 5 give?
>
>
>--
>Dave Hodgkinson, http://www.hodgkinson.org
>Editor
gards,
rene
- Original Message -
From: "Tim Samshuijzen" <[EMAIL PROTECTED]>
To: "René Tegel" <[EMAIL PROTECTED]>
Sent: Tuesday, February 06, 2001 1:58 PM
Subject: Re: amazingly slow
Dear René,
Thanks for your reply.
Oops, the 513 was a typing mistake.
Tim Samshuijzen <[EMAIL PROTECTED]> writes:
> This still does not tell me why the query is amazingly slow.
What else is happening on the system? what does, say, a vmstat 5 give?
--
Dave Hodgkinson, http://www.hodgkinson.org
Editor-in-chief, The Hig
;wordindex.word) ? I bet not.
>
>
>- Original Message -
>From: "Tim Samshuijzen" <[EMAIL PROTECTED]>
>To: <[EMAIL PROTECTED]>
>Sent: Tuesday, February 06, 2001 12:04 PM
>Subject: amazingly slow
>
>
>>
>>
>> Hello, I don'
t (0.01 sec)
This still does not tell me why the query is amazingly slow.
Tim
At 10:52 AM 6-2-2001 +, you wrote:
>Tim Samshuijzen <[EMAIL PROTECTED]> writes:
>
>> Anyone out there who wants to save me and our company?
>
>You missed the i
AIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Tuesday, February 06, 2001 12:04 PM
> Subject: amazingly slow
>
>
> >
> >
> > Hello, I don't understand why my queries are so incredibly slow.
> > We have MySQL on a 800MHz Linux machine w
Tim Samshuijzen <[EMAIL PROTECTED]> writes:
> Anyone out there who wants to save me and our company?
You missed the important first step: EXPLAIN the query.
--
Dave Hodgkinson, http://www.hodgkinson.org
Editor-in-chief, The Highway Star http://www.deep-pur
Hello, I don't understand why my queries are so incredibly slow.
We have MySQL on a 800MHz Linux machine with 513Mb.
Most queries look like this:
SELECT B.* FROM maintable AS M, wordindex AS YL1,
wordindex AS YL2, wordindex AS YL3
WHERE
YL1.Word = 'billy' AND
YL1.RecordNumber = M
14 matches
Mail list logo
