probably
want to look at your
network. Network latency can be the biggest culprit.
- Original Message -
From: Jan Gomes [EMAIL PROTECTED]
To: mysql mysql@lists.mysql.com
Cc: johnlist [EMAIL PROTECTED]
Sent: Friday, June 30, 2006 3:28 PM
Subject: Re: MySQL Denormalized
John Hicks
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 several
to look at your
network. Network latency can be the biggest culprit.
- Original Message -
From: Jan Gomes [EMAIL PROTECTED]
To: mysql mysql@lists.mysql.com
Cc: johnlist [EMAIL PROTECTED]
Sent: Friday, June 30, 2006 3:28 PM
Subject: Re: MySQL Denormalized
John Hicks wrote:
I don't see
-
From: Jan Gomes [EMAIL PROTECTED]
To: mysql mysql@lists.mysql.com
Cc: johnlist [EMAIL PROTECTED]
Sent: Friday, June 30, 2006 3:28 PM
Subject: Re: MySQL Denormalized
John Hicks wrote:
I don't see a question here.
But that won't stop me from giving a little advice :)
It is generally
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;
It has some method to
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;