h response time you are trying to keep to .01 or lower. If
it's end to end, you probably
want to look at your
network. Network latency can be the biggest culprit.
- Original Message -
From: "Jan Gomes" <[EMAIL PROTECTED]>
To: "mysql"
Cc: "johnlist&q
> it's end to end, you probably
want to look at your
> network. Network latency can be the biggest culprit.
>
> - Original Message -
> From: "Jan Gomes" <[EMAIL PROTECTED]>
> To: "mysql"
> Cc: "johnlist" <[EMAIL PROTECTED]>
>
r. If it's end to end, you probably want to look at your
network. Network latency can be the biggest culprit.
- Original Message -
From: "Jan Gomes" <[EMAIL PROTECTED]>
To: "mysql"
Cc: "johnlist" <[EMAIL PROTECTED]>
Sent: Friday, June 30, 20
John Hicks wrote:
>I don't see a question here.
>
>But that won't stop me from giving a little advice :)
>
>It is generally more important to keep things simple (by not
>denormalizing) than to try to optimize performance by complicating
>things significantly.
>
>Moreover, I can't see how combining
Jan Gomes wrote:
Hy Guys,
I needed denormalized my table to obtain high performance, but i want best
appropriate the space.
I joint two column (of the JOIN) intro one column with two separadores (# and ;)
Example:
ID | column_1 | column_denormalized
1 | Test | 1#20202;5#1000101;
I
