Skip navigation links

MySQL Forums :: Performance :: Correlated subquery taking much much longer since upgrade from 5.0


Advanced Search

Re: Correlated subquery taking much much longer since upgrade from 5.0
Posted by: Alan Douglas ()
Date: July 05, 2012 05:04AM

Thank you for taking the time to look at this.

I don't believe the problem is the client. 5.0, 5.1, and 5.5 are on three different machines, and we are using the local client on each machine. We also see the same problem using perl DBI.

The 5.1 is on a recent new install of Ubuntu 10.04 with no previous MySQL versions on it. The 5.5 is on a brand new install of Ubuntu 12.04 on a brand new machine set up specifically to investigate this.

Pehaps your 4s time was the result of the query cache? If not, then I'd be interested to know more about your setup.

Using the 5.1 client to connect to 5.1 server on same machine in the way you descibe yields a time of 75m58.949s

Options: ReplyQuote


Subject Views Written By Posted
Correlated subquery taking much much longer since upgrade from 5.0 875 Alan Douglas 07/03/2012 02:37PM
Re: Correlated subquery taking much much longer since upgrade from 5.0 460 Aftab Khan 07/04/2012 03:39AM
Re: Correlated subquery taking much much longer since upgrade from 5.0 422 Alan Douglas 07/04/2012 08:32AM
Re: Correlated subquery taking much much longer since upgrade from 5.0 449 Aftab Khan 07/05/2012 02:02AM
Re: Correlated subquery taking much much longer since upgrade from 5.0 488 Alan Douglas 07/05/2012 05:04AM
Re: Correlated subquery taking much much longer since upgrade from 5.0 488 Aftab Khan 07/05/2012 10:21AM
Re: Correlated subquery taking much much longer since upgrade from 5.0 538 Alan Douglas 07/06/2012 09:34AM
Re: Correlated subquery taking much much longer since upgrade from 5.0 513 Rick James 07/07/2012 06:12AM
Re: Correlated subquery taking much much longer since upgrade from 5.0 475 Aftab Khan 07/07/2012 08:42AM


Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.