From: Greg Smith <gsmith@gregsmith.com>
To: Kevin Murphy <murphy@genome.chop.edu>
Cc: pgsql-general@postgresql.org
Subject: Re: Drupal and PostgreSQL - performance issues?
Date: Tue, 14 Oct 2008 18:23:09 -0400 (EDT)
Message-ID: <Pine.GSO.4.64.0810141747240.5472@westnet.com> (raw)
In-Reply-To: <48F4B3C2.1050805@genome.chop.edu>
References: <2434A118-CEFA-43A9-BA88-006EC1F80326@hoegh.org>
<200810122214.53558.uwe@oss4u.com>
<20081013090228.248a665f@dawn.webthatworks.it>
<e7e0a2570810131945x1bbf10b8r67c0ac2a340b436f@mail.gmail.com>
<20081014114011.0ebe495a@dawn.webthatworks.it>
<3250B5B6-B507-4E79-BAF0-E98B73E9FED9@hoegh.org>
<Pine.GSO.4.64.0810140942010.28645@westnet.com>
<48F4B3C2.1050805@genome.chop.edu>
On Tue, 14 Oct 2008, Kevin Murphy wrote:
> One thing that might help people swallow the off-putting default "toy
> mode" performance of PostgreSQL would be an explanation of why
> PostgreSQL uses its shared memory architecture in the first place.
I doubt popularizing the boring technical details behind UNIX memory
allocation sematics would help do anything but reinforce PostgreSQL's
reputation for being complicated to setup. This same problem exists with
most serious databases, as everyone who has seen ORA-27123 can tell you.
What we need is a tool to help people manage those details if asked.
http://www.ibm.com/developerworks/db2/library/techarticle/dm-0509wright/
shows a good example; DB2's "probe" tool does this little bit of tuning
for you:
DB2 has automatically updated the "shmmax" kernel
parameter from "33554432" to the recommended value "268435456".
And you're off--it bumped that from the default 32MB to 256MB. The
problem for PostgreSQL is that nobody who is motivated enough to write
such magic for a large chunk of the supported platforms has had the time
to do it yet. I'll get to that myself eventually even if nobody else
does, as this is a recurring problem I'd like to make go away.
--
* Greg Smith gsmith@gregsmith.com http://www.gregsmith.com Baltimore, MD
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 using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: gsmith@gregsmith.com, murphy@genome.chop.edu, pgsql-general@postgresql.org
Subject: Re: Drupal and PostgreSQL - performance issues?
In-Reply-To: <Pine.GSO.4.64.0810141747240.5472@westnet.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