From: Josh Berkus <josh@agliodbs.com>
To: Frank Knobbe <frank@knobbe.us>
Cc: pgsql-performance@postgresql.org
Subject: Re: postgres 7.4 at 100%
Date: Mon, 28 Jun 2004 15:47:38 -0700
Message-ID: <200406281547.38742.josh@agliodbs.com> (raw)
In-Reply-To: <1088459215.551.18.camel@localhost>
References: <e071108e04062423591d2b8aa9@mail.gmail.com>
<200406281240.02954.josh@agliodbs.com>
<1088459215.551.18.camel@localhost>
Frank,
> I understand tuning PG is almost an art form, yet it should be based on
> actual usage patterns, not just by system dimensions, don't you agree?
Well, it's both. It's more that available RAM determines your *upper* limit;
that is, on Linux, you don't really want to have more than 20% allocated to
the shared_buffers or you'll be taking memory away from the kernel.
Within that limit, data size, query complexity and volume, and whether or not
you have long-running procedures tell you whether you're at the low end or
the high end.
To futher complicate things, these calculations are all going to change with
7.5.
--
-Josh Berkus
Aglio Database Solutions
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 using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: josh@agliodbs.com, frank@knobbe.us
Subject: Re: postgres 7.4 at 100%
In-Reply-To: <200406281547.38742.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