| From: | Greg Smith <gsmith(at)gregsmith(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Gregory Stark <stark(at)enterprisedb(dot)com>, jd(at)commandprompt(dot)com, Josh Berkus <josh(at)agliodbs(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Simple postgresql.conf wizard |
| Date: | 2008-12-04 00:34:50 |
| Message-ID: | Pine.GSO.4.64.0812031908570.781@westnet.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, 3 Dec 2008, Robert Haas wrote:
> I'm not sure if you've thought about this, but there is also a
> difference between max_connections and maximum LIKELY connections.
It's actually an implicit assumption of the model Josh threw out if you
stare at the numbers. The settings for work_mem are twice as high per
connection in the Web+OLTP application cases, based on the assumption that
you're just not going to get everybody doing sorting at once in those
situations. I toyed with exposing that as an explicit "connection load
duty factor", then remembered I was trying to deliver something rather
than tweak the parameters forever. It may be a bit too aggressive as
written right now in those cases.
--
* Greg Smith gsmith(at)gregsmith(dot)com http://www.gregsmith.com Baltimore, MD
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Smith | 2008-12-04 00:47:32 | Re: Simple postgresql.conf wizard |
| Previous Message | Joshua D. Drake | 2008-12-04 00:27:21 | Re: Simple postgresql.conf wizard |