Re: Lion and WO
Re: Lion and WO
- Subject: Re: Lion and WO
- From: John Huss <email@hidden>
- Date: Wed, 27 Jul 2011 14:30:03 -0500
Finding a weak spot in the query optimizer can be done for any database, can't it? That's just the nature of the beast.
On Wed, Jul 27, 2011 at 2:22 PM, Kieran Kelleher
<email@hidden> wrote:
Good detail. Thanks for the insight. And yeah, it was obvious from the beginning that you loathed MySQL! ;-)
Cheers, Kieran
On Jul 27, 2011, at 2:21 PM, Andrew Satori wrote:
>
> You asked, about rows and columns so I answered. I know what killed it. I know why. I know what I could have done to prevent it and work around it. The net result is that in order to get the performance I needed, I was going to have to alter things to be MySQL specific, rather than the standard syntax that works across multiple backends. Hardware was not the limit. The data in question was in how MySQL coped with a 5th normal structure and pulling in detail information associated with a master entry record. The problems stemmed from the join and a table scan caused my MySQL's inability properly user the index. The same request against the same data in every other platform of note executed better than 2x as fast as the MySQL implementation, in some cases on the same hardware, but most on inferior hardware.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden