PROTECTED]
Sent: Thursday, December 23, 2004 9:37 AM
Subject: Re: scanning 2 rows slow index fast 26GB MyISAM
Thanks Leo,
However, remember that the key returns quickly on index-only queries, so
the conditions in the WHERE are not the problem. I want to know why it
takes 5 mins to scan 2 rows
: Thursday, December 23, 2004 9:00 AM
Subject: Re: Re: scanning 2 rows slow index fast 26GB MyISAM
Bryan Heitman,
Because it should scan through all the table to get all records,so it takes
so a long time,i think.
=== 2004-12-23 09:37:00 ===
Thanks Leo,
However, remember that the key
Bryan,
Can you send the output of show create table matrix? You've just sent
the location table output, but your select command refers to a table
called matrix.
[]s,
Sergio.
On Wed, 22 Dec 2004, Bryan Heitman wrote:
I am experiencing extreme slowness performing a query in which 2 rows are
.disk2/SQL/search/'
- Original Message -
From: Sergio Salvi [EMAIL PROTECTED]
To: Bryan Heitman [EMAIL PROTECTED]
Cc: mysql@lists.mysql.com
Sent: Thursday, December 23, 2004 10:08 AM
Subject: Re: scanning 2 rows slow index fast 26GB MyISAM
Bryan,
Can you send the output of show create table
On Thu, 23 Dec 2004, Bryan Heitman wrote:
My mistake! Here you go:
Ok, no prob :)
CREATE TABLE `matrix` (
`WordID` int(11) unsigned NOT NULL default '0',
`LocationID` int(11) unsigned NOT NULL default '0',
`Position` enum('Body','From','Subject','To','Mailbox','File') NOT NULL
: mysql@lists.mysql.com
Sent: Thursday, December 23, 2004 12:01 PM
Subject: Re: scanning 2 rows slow index fast 26GB MyISAM
On Thu, 23 Dec 2004, Bryan Heitman wrote:
My mistake! Here you go:
Ok, no prob :)
CREATE TABLE `matrix` (
`WordID` int(11) unsigned NOT NULL default '0',
`LocationID` int(11
On Thursday 23 December 2004 02:01 pm, Bryan Heitman wrote:
Hi Sergio,
All of your suggestions deal with key optimization, I do not believe I have
a key issue here. Remember that select count(*), an index-only query
returns in .06 seconds which is very quick. The real question, is why does
Bryan Heitman wrote:
I am experiencing extreme slowness performing a query in which 2 rows
are returned hanging in the sending data status.
Performing an index only query such as SELECT COUNT(*) is extremely
quick so I know the only extra step is retrieving the data from the MYD.
I am looking
a theory.
Donny
-Original Message-
From: Bryan Heitman [mailto:[EMAIL PROTECTED]
Sent: Thursday, December 23, 2004 2:02 PM
To: Sergio Salvi
Cc: mysql@lists.mysql.com
Subject: Re: scanning 2 rows slow index fast 26GB MyISAM
Hi Sergio,
All of your suggestions deal with key
Heitman' [EMAIL PROTECTED]; 'Sergio Salvi'
[EMAIL PROTECTED]
Cc: mysql@lists.mysql.com
Sent: Thursday, December 23, 2004 2:49 PM
Subject: RE: scanning 2 rows slow index fast 26GB MyISAM
Bryan,
Select count(*) is basically a different query then select locationid or
any
of your fields. I have tables
I am experiencing extreme slowness performing a query in which 2 rows are
returned hanging in the sending data status.
Performing an index only query such as SELECT COUNT(*) is extremely quick so
I know the only extra step is retrieving the data from the MYD.
I am looking for thoughts on why
11 matches
Mail list logo