From: Greg Stark <gsstark@mit.edu>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Jenny Zhang <jenny@osdl.org>
Cc: pgsql-performance@postgresql.org
Subject: Re: osdl-dbt3 run results - puzzled by the execution plans
Date: 19 Sep 2003 09:12:27 -0400
Message-ID: <87fzis2a84.fsf@stark.dyndns.tv> (raw)
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>
Tom Lane <tgl@sss.pgh.pa.us> writes:
> 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%.
I think the reason he gets good repeatability is because he's talking about
the aggregate results for a whole test run. Not individual queries. In theory
you could just run the whole test multiple times. The more times you run it
the lower the variation in the total run time would be.
Actually, the variation in run time is also a useful statistic, both for
postgres and the kernel. It might be useful to do multiple complete runs and
keep track of the average standard deviation of the time required for each
step.
Higher standard deviation implies queries can't be reliably depended on not to
take inordinately long, which can be a problem for some working models. For
the kernel it could mean latency issues or it could mean the swapper or buffer
cache was overly aggressive.
--
greg
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: gsstark@mit.edu, tgl@sss.pgh.pa.us, jenny@osdl.org
Subject: Re: osdl-dbt3 run results - puzzled by the execution plans
In-Reply-To: <87fzis2a84.fsf@stark.dyndns.tv>
References: <1063924610.31150.75.camel@ibm-a.pdx.osdl.net> <8224.1063941637@sss.pgh.pa.us> <87fzis2a84.fsf@stark.dyndns.tv>
* 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