Hello Victor,
> What version of MySQL are you using? Have you
> checked the cardinality on
> these tables?
Problem solved! Optimizing the table brought the query
time down to 17 secs Wow!
Thanks for the input Victor and merci to Arnaud for
the quick fix.
Patrick
___
What version of MySQL are you using? Have you checked the cardinality on
these tables?
-Original Message-
From: Patrick Drouin
To: [EMAIL PROTECTED]
Sent: 7/15/04 8:27 AM
Subject: Need help optimizing query
Hello everyone,
I'm having a hard time with the following query. It
retrieves ab
Bonjour Arnaud,
--- Arnaud <[EMAIL PROTECTED]> wrote:
> On 15 Jul 2004 at 6:27, Patrick Drouin
> Your indexes look good, but I see that you have some
> varchar fields.
> Maybe
> you could run an "optimize table" on these tables?
I'm running it at the moment, I will follow-up on the
list when it'
On 15 Jul 2004 at 6:27, Patrick Drouin <[EMAIL PROTECTED]>
wrote:
> I'm having a hard time with the following query. It
> retrieves about 3K rows from a few tables. One of them
> contains over 40M rows. When run on a 3Ghz server with
> 1G of RAM it returns the rows in more than 1 mini. I
> don't
Absolutely! I have multiple indexes. I think it might be a problem with ODBC
> Are your tables indexed? http://www.mysql.com/doc/en/MySQL_indexes.html
>
> Saqib Ali
> -
> http://www.xml-dev.com
>
>
-
Visit CARMEL MUSIC & ENTERTAINMENT we
Are your tables indexed? http://www.mysql.com/doc/en/MySQL_indexes.html
Saqib Ali
-
http://www.xml-dev.com
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
2 PM
> To: [EMAIL PROTECTED]
> Cc: [EMAIL PROTECTED]
> Subject: RE: Need help optimizing query, awfully slow on only
> 2 records
>
>
> When following query is pulled up, it takes about whole 1-2
> minutes to come up. "inquiries" table has 17000 records,
> &
ilto:[EMAIL PROTECTED]
> Sent: Wednesday, August 20, 2003 3:14 PM
> To: Michael S. Fischer
> Cc: [EMAIL PROTECTED]
> Subject: RE: Need help optimizing query, awfully slow on only
> 2 records
>
>
>
> Result of EXPLAIN is:
> table|type|possible_keys|key|key_len|ref|ro
; > Sent: Wednesday, August 20, 2003 3:14 PM
> > To: Michael S. Fischer
> > Cc: [EMAIL PROTECTED]
> > Subject: RE: Need help optimizing query, awfully slow on only
> > 2 records
> >
> >
> >
> > Result of EXPLAIN is:
> > table|type|poss
Query takes 3.4 seconds to run on the server, but it takes 1-2minutes to run via
MyODBC 3.51.06 using passthrough (Access97 is the front end, but it has query
type that allows bypass of Access interpretation.
> Two Questions:
>
> Is the same query running directly on the linux server thru mysql i
ment) [mailto:[EMAIL PROTECTED]
> > Sent: Wednesday, August 20, 2003 2:52 PM
> > To: [EMAIL PROTECTED]
> > Cc: [EMAIL PROTECTED]
> > Subject: RE: Need help optimizing query, awfully slow on only
> > 2 records
> >
> >
> > When following query is pull
When following query is pulled up, it takes about whole 1-2 minutes to come up.
"inquiries" table has 17000 records, "contacts" has about 7000,
"individual_contacts" has about 16000.
It has gotten worse once I upgraded to 4.0 and latest MyODBC.
Clients are separate machines (mix of Win98 and WinXP)
What are you defining as a huge performance hit?
Is the result set 20K records, or the base tables? How big are the base
tables?
Are the client and server on the same machine? Pulling 20K records across
the network could take some time. Formatting 20K records into a pull -down
list in access will
13 matches
Mail list logo