From: Tom Lane <tgl@sss.pgh.pa.us>
To: Matthew T. O'Connor <matthew@zeut.net>
Cc: pgsql-hackers@postgresql.org
Subject: Re: Changing the default configuration (was Re: [pgsql-advocacy] PostgreSQL Benchmarks)
Date: Tue, 11 Feb 2003 14:06:32 -0500
Message-ID: <27295.1044990392@sss.pgh.pa.us> (raw)
In-Reply-To: <1044989631.32185.151.camel@zeutrh80>
References: <303E00EBDD07B943924382E153890E5434A909@cuthbert.rcsinc.local>
<26004.1044980414@sss.pgh.pa.us>
<49391.192.168.1.12.1044985098.squirrel@mail.mayuli.com>
<26924.1044986473@sss.pgh.pa.us>
<1044989631.32185.151.camel@zeutrh80>
"Matthew T. O'Connor" <matthew@zeut.net> writes:
> ... So we ship postgresql.conf with 32M of
> shared memory and auto_shared_mem_reduction = true. With a comment that
> the administrator might want to turn this off for production.
This really doesn't address Justin's point about clueless benchmarkers,
however. In fact I fear it would make that problem worse: if Joe Blow
says he got horrible performance, who knows whether he was running with
a reasonable number of buffers or not? Especially when you ask him
"did you have lots of shared buffers" and he responds "yes, of course,
it says 32M right here".
We've recently been moving away from the notion that it's okay to
silently lose functionality in order to run on a given system. For
example, if you want to install without readline, you now have to
explicitly tell configure that, because we heard "why don't I have
history in psql" way too often from people who just ran configure
and paid no attention to what it told them.
I think that what this discussion is really leading up to is that we
are going to decide to apply the same principle to performance. The
out-of-the-box settings ought to give reasonable performance, and if
your system can't handle it, you should have to take explicit action
to acknowledge the fact that you aren't going to get reasonable
performance.
regards, tom lane
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: tgl@sss.pgh.pa.us, matthew@zeut.net, pgsql-hackers@postgresql.org
Subject: Re: Changing the default configuration (was Re: [pgsql-advocacy] PostgreSQL Benchmarks)
In-Reply-To: <27295.1044990392@sss.pgh.pa.us>
References: <303E00EBDD07B943924382E153890E5434A909@cuthbert.rcsinc.local> <26004.1044980414@sss.pgh.pa.us> <49391.192.168.1.12.1044985098.squirrel@mail.mayuli.com> <26924.1044986473@sss.pgh.pa.us> <1044989631.32185.151.camel@zeutrh80> <27295.1044990392@sss.pgh.pa.us>
* 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