From: | Greg Smith <gsmith(at)gregsmith(dot)com> |
---|---|
To: | pgsql-performance(at)postgresql(dot)org |
Subject: | Re: PostgreSQL Configuration Tool for Dummies |
Date: | 2007-06-26 18:14:24 |
Message-ID: | Pine.GSO.4.64.0706261401240.6715@westnet.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
On Tue, 26 Jun 2007, Josh Berkus wrote:
> The problem is that there are no "safe, middle-of-the-road" values for some
> things, particularly max_connections and work_mem.
Your max_connections concern is one fact that haunts the idea of just
giving out some sample configs for people. Lance's tool asks outright the
expectation for max_connections which I think is the right thing to do.
> Web app, typical machine:
> work_mem = 256kb
> default_statistics_target=100
> autovacuum=on
> Reporting app, same machine:
> work_mem = 32mb
> default_statistics_target=500
> autovacuum=off
I think people are stuck with actually learning a bit about work_mem
whether they like it or not, because it's important to make it larger but
we know going too high will be a problem with lots of connections doing
sorts.
As for turning autovacuum on/off and the stats target, I'd expect useful
defaults for those would come out of how the current sample is asking
about read vs. write workloads and expected database size. Those simple
to understand questions might capture enough of the difference between
your two types here.
--
* Greg Smith gsmith(at)gregsmith(dot)com http://www.gregsmith.com Baltimore, MD
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2007-06-26 18:49:06 | Re: Database-wide VACUUM ANALYZE |
Previous Message | Steven Flatt | 2007-06-26 17:25:44 | Re: Database-wide VACUUM ANALYZE |