X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [64.117.224.130]) by svr1.postgresql.org (Postfix) with ESMTP id 727E4D1B50F for ; Fri, 19 Sep 2003 13:12:58 +0000 (GMT) Received: from svr1.postgresql.org ([64.117.224.193]) by localhost (neptune.hub.org [64.117.224.130]) (amavisd-new, port 10024) with ESMTP id 34570-06 for ; Fri, 19 Sep 2003 10:12:29 -0300 (ADT) Received: from smtp.istop.com (dci.doncaster.on.ca [66.11.168.194]) by svr1.postgresql.org (Postfix) with ESMTP id 7EA4ED1B4E5 for ; Fri, 19 Sep 2003 10:12:25 -0300 (ADT) Received: from stark.dyndns.tv (gsstark.mtl.istop.com [66.11.160.162]) by smtp.istop.com (Postfix) with ESMTP id 1D24136956; Fri, 19 Sep 2003 09:12:29 -0400 (EDT) Received: from localhost ([127.0.0.1] helo=stark.dyndns.tv ident=foobar) by stark.dyndns.tv with smtp (Exim 3.36 #1 (Debian)) id 1A0L3k-0004c7-00; Fri, 19 Sep 2003 09:12:28 -0400 To: Tom Lane Cc: Jenny Zhang , pgsql-performance@postgresql.org Subject: Re: osdl-dbt3 run results - puzzled by the execution plans References: <1063924610.31150.75.camel@ibm-a.pdx.osdl.net> <8224.1063941637@sss.pgh.pa.us> In-Reply-To: <8224.1063941637@sss.pgh.pa.us> From: Greg Stark Organization: The Emacs Conspiracy; member since 1992 Date: 19 Sep 2003 09:12:27 -0400 Message-ID: <87fzis2a84.fsf@stark.dyndns.tv> Lines: 24 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200309/284 X-Sequence-Number: 3650 Tom Lane 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