pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Jenny Zhang <jenny@osdl.org>
Cc: pgsql-performance@postgresql.org
Subject: Re: osdl-dbt3 run results - puzzled by the execution plans
Date: Thu, 18 Sep 2003 23:20:37 -0400
Message-ID: <8224.1063941637@sss.pgh.pa.us> (raw)
In-Reply-To: <1063924610.31150.75.camel@ibm-a.pdx.osdl.net>
References: <1063924610.31150.75.camel@ibm-a.pdx.osdl.net>

Jenny Zhang <jenny@osdl.org> writes:
> ...  It seems to me that small 
> effective_cache_size favors the choice of nested loop joins (NLJ) 
> while the big effective_cache_size is in favor of merge joins (MJ).  

No, I wouldn't think that, because a nestloop plan will involve repeated
fetches of the same tuples whereas a merge join doesn't (at least not
when it sorts its inner input, as this plan does).  Larger cache
improves the odds of a repeated fetch not having to do I/O.  In practice
a larger cache area would also have some effects on access costs for the
sort's temp file, but I don't think the planner's cost model for sorting
takes that into account.

As Matt Clark points out nearby, the real question is whether these
planner estimates have anything to do with reality.  EXPLAIN ANALYZE
results would be far more interesting than plain EXPLAIN.

> However, within the same run set consist of 6 runs, we see 2-3% 
> standard deviation for the run metrics associated with the multiple
> stream part of the test (as opposed to the single stream part).

<python> Och, laddie, we useta *dream* of 2-3% variation </python>

> We would like to reduce the variation to be less than 1% so that a 
> 2% change between two different kernels would be significant. 

I think this is a pipe dream.  Variation in where the data gets laid
down on your disk drive would alone create more than that kind of delta.
I'm frankly amazed you could get repeatability within 2-3%.

			regards, tom lane



view thread (12+ messages)  latest in thread

Message-ID: <8224.1063941637@sss.pgh.pa.us>
Permalink:  ../8224.1063941637@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/8224.1063941637@sss.pgh.pa.us

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-performance@postgresql.org
  Cc: tgl@sss.pgh.pa.us, jenny@osdl.org
  Subject: Re: osdl-dbt3 run results - puzzled by the execution plans
  In-Reply-To: <8224.1063941637@sss.pgh.pa.us>
  References: <1063924610.31150.75.camel@ibm-a.pdx.osdl.net> <8224.1063941637@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox