From: Greg Smith <gsmith@gregsmith.com>
To: Mikkel Høgh <mikkel@hoegh.org>
Cc: pgsql-general@postgresql.org
Subject: Re: Drupal and PostgreSQL - performance issues?
Date: Tue, 14 Oct 2008 10:02:26 -0400 (EDT)
Message-ID: <Pine.GSO.4.64.0810140942010.28645@westnet.com> (raw)
In-Reply-To: <3250B5B6-B507-4E79-BAF0-E98B73E9FED9@hoegh.org>
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>
On Tue, 14 Oct 2008, Mikkel Høgh wrote:
> You are targetting DBAs using servers with less than 512 MB RAM. Is
> PostgreSQL supposed to be used by professional DBAs on enterprise
> systems or is it supposed to run out of the box on my old Pentium 3?
Take a look at http://bugzilla.kernel.org/show_bug.cgi?id=11381
There you'll discover that the Linux default for how much memory an
application like PostgreSQL can allocate is 32MB. This is true even if
you install the OS on a system with 128GB of RAM. If PostgreSQL created a
default configuration optimized for "enterprise systems", that
configuration wouldn't even start on *any* Linux system with the default
kernel settings. The above is an attempt to change that, rejected with
the following text that aptly describes the default PostgreSQL
configuration as well: "The requirement is that SHMMAX is sane for the
user by default and that means *safe* rather than as big as possible".
The situation on most other operating systems is similarly bad.
So the dichotomy here is even worse than you think: it's not just that
the performance profile would be wrong, it's that defaults targeting
modern hardware would make it so the database won't even start on your old
Pentium 3. The best the PostgreSQL community can do is provide
documentation on how you re-tune your *operating system first*, then the
database server, to get good performance on systems with modern amounts of
RAM.
Admittedly, that documentation and related support tools should be better,
mainly by being easier to find. This discussion is well timed in that I
was planning this month to propose adding a URL with a tuning guide and/or
sample configurations to the top of the postgresql.conf file before the
next release comes out; when that comes up I can point to this thread as a
reminder of why that's needed.
--
* 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, mikkel@hoegh.org, pgsql-general@postgresql.org
Subject: Re: Drupal and PostgreSQL - performance issues?
In-Reply-To: <Pine.GSO.4.64.0810140942010.28645@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