select * from TableName LIMIT NumberOfRows
George Christoforakis
- Original Message -
From: Maurice Coyle
To: [EMAIL PROTECTED]
Sent: Friday, June 27, 2003 12:34 PM
Subject: very long query time
hi all,
i have a table in my mysql database with around 66
Hi Maurice,
I would be interested to see how your SQL reuqest looks like. Perhaps it is
possible to optimize at this point, just a guess so.
Best regards
Nils Valentin
Tokyo/Japan
2003 6 27 18:34Maurice Coyle :
hi all,
i have a table in my mysql database with around 66 million rows in it.
On Friday, June 27, 2003, at 05:34 AM, Maurice Coyle wrote:
i have a table in my mysql database with around 66 million rows in
it. when i query this table, it takes anywhere from 3 minutes to 10
minutes to return the results. i've tried this both from within the
mysql command line and from
Part of the problem may be the size of the returned set. If you are
having MySQL return the date on 11K rows, your bottleneck may be the
network or disk. Remeber, MySQL has to read all that data from the
database and transfer to your program or display it for the command
line. Even if you had
I have had similar performance concerns, but on a much smaller scale.
The data was well indexed, but took far too long to query (particularly
with aggregate queries).
Check the individual row size of your table. In my case, I had a TEXT
field that would frequently be fairly long. Moving that
PROTECTED]
Subject: RE: very long query time
I have had similar performance concerns, but on a much smaller scale.
The data was well indexed, but took far too long to query (particularly
with aggregate queries).
Check the individual row size of your table. In my case, I had a TEXT
field that would
:33 AM
To: [EMAIL PROTECTED]
Subject: RE: very long query time
I have had similar performance concerns, but on a much smaller scale.
The data was well indexed, but took far too long to query (particularly
with aggregate queries).
Check the individual row size of your table. In my case, I had a TEXT
This is a shot in the dark, but perhaps you need to optimize your
indexes. By default, MySQL assumes an even distribution of values for
indexes. I'm not sure when it diverges from this default, I assume it
does at some point. MySQL uses the data distribution values/assumptions
to determine how
