X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (developer.postgresql.org [64.117.224.193]) by svr1.postgresql.org (Postfix) with ESMTP id 9AD87B43183 for ; Sat, 5 Jul 2003 22:59:37 +0000 (GMT) Received: from svr1.postgresql.org ([64.117.224.193]) by localhost (svr1.postgresql.org [64.117.224.193]) (amavisd-new, port 10024) with ESMTP id 93963-03 for ; Sat, 5 Jul 2003 19:59:26 -0300 (ADT) Received: from davinci.ethosmedia.com (unknown [209.10.40.251]) by svr1.postgresql.org (Postfix) with ESMTP id CF5B7B4316A for ; Sat, 5 Jul 2003 19:59:25 -0300 (ADT) Received: from [63.195.55.98] (HELO temoku) by davinci.ethosmedia.com (CommuniGate Pro SMTP 4.0.2) with ESMTP id 3186164; Sat, 05 Jul 2003 15:59:43 -0700 Content-Type: text/plain; charset="iso-8859-1" From: Josh Berkus Reply-To: josh@agliodbs.com Organization: Aglio Database Solutions To: Sean Chittenden Subject: Re: Moving postgresql.conf tunables into 2003... Date: Sat, 5 Jul 2003 15:58:25 -0700 User-Agent: KMail/1.4.3 Cc: pgsql-performance@postgresql.org References: <20030703190502.GR72567@perrin.int.nxad.com> <200307031938.15357.josh@agliodbs.com> <20030705211256.GY72567@perrin.int.nxad.com> In-Reply-To: <20030705211256.GY72567@perrin.int.nxad.com> MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Message-Id: <200307051558.25484.josh@agliodbs.com> X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200307/102 X-Sequence-Number: 2395 Sean, > The SGML docs aren't in the DBA's face and are way out of the way for > DBAs rolling out a new system or who are tuning the system. SGML =3D=3D > Developer, conf =3D=3D DBA. That's exactly my point. We cannot provide enough documentation in the CON= F=20 file without septupling its length. IF we remove all commentary, and inste= ad=20 provide a pointer to the documentation, more DBAs will read it. > Some of those parameters are based on > hardware constraints and should be pooled and organized as such. >=20 > random_page_cost =3D=3D > avg cost of a random disk seek/read (eg: disk seek time) =3D=3D > constant integer for a given piece of hardware But, you see, this is exactly what I'm talking about. random_page_cost is= n't=20 static to a specific piece of hardware ... it depends as well on what else = is=20 on the disk/array, concurrent disk activity, disk controller settings,=20 filesystem, OS, distribution of records and tables, and arrangment of the= =20 partitions on disk. One can certainly get a "good enough" value by=20 benchmarking the disk's random seek and calculating based on that ... but t= o=20 get an "ideal" value requires a long interactive session by someone with=20 experience and in-depth knowledge of the machine and database. > There are other settings that are RAM based as well, which should be > formulaic and derived though a formula hasn't been defined to date. You seem pretty passionate about this ... how about you help me an Kevin=20 define a benchmarking suite when I get back into the country (July 17)? I= f=20 we're going to define formulas, it requires that we have a near-comprehensi= ve=20 and consistent test database and test battery that we can run on a variety = of=20 machines and platforms. --=20 -Josh Berkus ______AGLIO DATABASE SOLUTIONS___________________________ Josh Berkus Complete information technology josh@agliodbs.com and data management solutions (415) 565-7293 for law firms, small businesses fax 621-2533 and non-profit organizations. San Francisco