X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 606D18B9E20 for ; Tue, 1 Feb 2005 06:06:25 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 13261-03 for ; Tue, 1 Feb 2005 06:06:22 +0000 (GMT) Received: from flake.decibel.org (flake.decibel.org [66.143.173.58]) by svr1.postgresql.org (Postfix) with ESMTP id CC4A78B9E1C for ; Tue, 1 Feb 2005 06:06:22 +0000 (GMT) Received: by flake.decibel.org (Postfix, from userid 1001) id D209A1C90B; Tue, 1 Feb 2005 00:06:20 -0600 (CST) Date: Tue, 1 Feb 2005 00:06:20 -0600 From: "Jim C. Nasby" To: Tom Lane Cc: josh@agliodbs.com, Markus Schaber , Christopher Kings-Lynne , PostgreSQL Performance List Subject: Re: Automagic tuning Message-ID: <20050201060620.GE32356@decibel.org> References: <20040727151531.4f60b5b0@kingfisher.intern.logi-track.com> <41066485.7080502@familyhealth.com.au> <41FE4692.6080104@logi-track.com> <200501311209.31827.josh@agliodbs.com> <3900.1107203172@sss.pgh.pa.us> <20050201045211.GB32356@decibel.org> <10114.1107234387@sss.pgh.pa.us> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <10114.1107234387@sss.pgh.pa.us> X-Operating-System: FreeBSD 4.10-RELEASE-p3 i386 X-Distributed: Join the Effort! http://www.distributed.net User-Agent: Mutt/1.5.6i X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.023 tagged_above=0 required=5 tests=AWL X-Spam-Level: X-Archive-Number: 200502/7 X-Sequence-Number: 10336 On Tue, Feb 01, 2005 at 12:06:27AM -0500, Tom Lane wrote: > "Jim C. Nasby" writes: > > On Mon, Jan 31, 2005 at 03:26:12PM -0500, Tom Lane wrote: > >> Preferably a whole lot of queries. All the measurement techniques I can > >> think of are going to have a great deal of noise, so you shouldn't > >> twiddle these cost settings based on just a few examples. > > > Are there any examples of how you can take numbers from pg_stats_* or > > explain analize and turn them into configuration settings (such and > > random page cost)? > > Well, the basic idea is to adjust random_page_cost so that the ratio of > estimated cost to real elapsed time (as shown by EXPLAIN ANALYZE) is the > same for seqscans and indexscans. What you have to watch out for is > that the estimated cost model is oversimplified and doesn't take into > account a lot of real-world factors, such as the activity of other > concurrent processes. The reason for needing a whole lot of tests is > essentially to try to average out the effects of those unmodeled > factors, so that you have a number that makes sense within the planner's > limited view of reality. Given that, I guess the next logical question is: what would it take to collect stats on queries so that such an estimate could be made? And would it be possible/make sense to gather stats useful for tuning the other parameters? -- Jim C. Nasby, Database Consultant decibel@decibel.org Give your computer some brain candy! www.distributed.net Team #1828 Windows: "Where do you want to go today?" Linux: "Where do you want to go tomorrow?" FreeBSD: "Are you guys coming, or what?"