Richard Huxton <[EMAIL PROTECTED]> writes:
> Which says to me that your form is fine. Testing says otherwise, so there must
> be some element of the query that is not being accounted for in EXPLAIN
> ANALYSE.
To wit, planning time. EXPLAIN ANALYZE only counts execution time.
And planning time
Richard -
Your analysis of this looks right on, to me. With current code,
if you put in explicit JOINS, the table get joined in that order,
no questions. By specifying an all JOIN version, you've made the
optimizers job very easy: only one plan to consider.
Your point about realistic data and co
On Friday 06 Sep 2002 11:59 am, [EMAIL PROTECTED] wrote:
> Has the performance for queries with lots of joins (more than 5) been
> improved in v7.2 ?
>
> I'm using 7.0.3 on Redhat 7.1 on a K2-6 500 CPU, and it is about 3 times
> slower than MySQL, or Access on windoze platform :-(
>
> I tried diff
Has the performance for queries with lots of joins (more than 5) been
improved in v7.2 ?
I'm using 7.0.3 on Redhat 7.1 on a K2-6 500 CPU, and it is about 3 times
slower than MySQL, or Access on windoze platform :-(
I tried different command-line optimisations, and got the best results (on
oth
