From: Josh Berkus <josh@agliodbs.com>
To: Sean Chittenden <sean@chittenden.org>
Cc: pgsql-performance@postgresql.org
Subject: Re: Moving postgresql.conf tunables into 2003...
Date: Sat, 5 Jul 2003 15:58:25 -0700
Message-ID: <200307051558.25484.josh@agliodbs.com> (raw)
In-Reply-To: <20030705211256.GY72567@perrin.int.nxad.com>
References: <20030703190502.GR72567@perrin.int.nxad.com>
<200307031938.15357.josh@agliodbs.com>
<20030705211256.GY72567@perrin.int.nxad.com>
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 ==
> Developer, conf == DBA.
That's exactly my point. We cannot provide enough documentation in the CONF
file without septupling its length. IF we remove all commentary, and instead
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.
>
> random_page_cost ==
> avg cost of a random disk seek/read (eg: disk seek time) ==
> constant integer for a given piece of hardware
But, you see, this is exactly what I'm talking about. random_page_cost isn't
static to a specific piece of hardware ... it depends as well on what else is
on the disk/array, concurrent disk activity, disk controller settings,
filesystem, OS, distribution of records and tables, and arrangment of the
partitions on disk. One can certainly get a "good enough" value by
benchmarking the disk's random seek and calculating based on that ... but to
get an "ideal" value requires a long interactive session by someone with
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
define a benchmarking suite when I get back into the country (July 17)? If
we're going to define formulas, it requires that we have a near-comprehensive
and consistent test database and test battery that we can run on a variety of
machines and platforms.
--
-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
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: josh@agliodbs.com, sean@chittenden.org
Subject: Re: Moving postgresql.conf tunables into 2003...
In-Reply-To: <200307051558.25484.josh@agliodbs.com>
References: <20030703190502.GR72567@perrin.int.nxad.com> <200307031938.15357.josh@agliodbs.com> <20030705211256.GY72567@perrin.int.nxad.com> <200307051558.25484.josh@agliodbs.com>
* 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