Shawn,
Thank you very much for your tips.
I´ll do that.
Ronan
- Original Message -
From: <[EMAIL PROTECTED]>
To: "Ronan Lucio" <[EMAIL PROTECTED]>
Cc:
Sent: Tuesday, January 18, 2005 6:36 PM
Subject: Re: Doubt about Performance
"Ronan Lucio" <[EMAIL
> -Original Message-
> From: Ronan Lucio [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, January 18, 2005 10:13 AM
> To: mysql@lists.mysql.com
> Subject: Doubt about Performance
>
> Hello,
>
> Trying to keep the database and the application fast, I´d
> like to clearify my mind about it
"Ronan Lucio" <[EMAIL PROTECTED]> wrote on 01/18/2005 02:53:39 PM:
> Shawn,
>
> Your tips are realy good but I can´t use cache neither for
> queries nor for pages because our site serves hundreds of
> clients, each one with your own code make a different
> query, returning different rows.
>
> It
Sasha,
> I assume you mean "has serious performance impact" when you say "weight".
If
> this is not what you meant, please correct/clarify.
Yes, you´re right.
>>
>> 1) Is a SELECT DISTINCT over 5,000 records a weight
>> query? (Supposing it has about 20 different option the the
>> DISTIN
"Ronan Lucio" <[EMAIL PROTECTED]> wrote on 01/18/2005 01:13:10 PM:
> Hello,
>
> Trying to keep the database and the application fast,
> I´d like to clearify my mind about it.
>
> 1) Is a SELECT DISTINCT over 5,000 records a weight
> query? (Supposing it has about 20 different option the the
Ronan Lucio wrote:
Hello,
Trying to keep the database and the application fast,
I´d like to clearify my mind about it.
Ronan:
I assume you mean "has serious performance impact" when you say "weight". If
this is not what you meant, please correct/clarify.
1) Is a SELECT DISTINCT over 5,000 records
Greg,
Thank you very much for your help.
> An index the full size of the distinct key is probably very quick
especially
> if it only has 20 distinct values. OTOH, if you already know you have a
> small number of distinct values, could you just store them normalized in a
> different table?
Actua
