Skip site navigation (1) Skip section navigation (2)

Re: A smaller default postgresql.conf

From: Josh Berkus <josh(at)agliodbs(dot)com>
To: Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Joshua Drake <jd(at)commandprompt(dot)com>, Hans-Juergen Schoenig <postgres(at)cybertec(dot)at>, Peter Eisentraut <peter_e(at)gmx(dot)net>, Magnus Hagander <magnus(at)hagander(dot)net>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: A smaller default postgresql.conf
Date: 2008-08-28 18:21:41
Message-ID: 48B6ECB5.5080307@agliodbs.com (view raw or flat)
Thread:
Lists: pgsql-hackers
Kevin,

> # maintenance_work_mem = 256MB  #webserver with 2GB RAM

Well, that was before multiple autovacuum workers. Now, you'd want it 
lower.  But ... it's better for vacuum to finish quickly than to drag 
on.  Vacuum uses more I/O than it does RAM.

> But I'm amazed by this, too:
>  
> # max_connections = 700  # web application database
>  
> How many CPUs and spindles are you assuming there?

I'm assuming that the user isn't using connection pooling, and 7/8 of 
those connections will be idle at any given time.

--Josh

In response to

pgsql-hackers by date

Next:From: Josh BerkusDate: 2008-08-28 18:23:01
Subject: Re: A smaller default postgresql.conf
Previous:From: Tom LaneDate: 2008-08-28 17:59:59
Subject: WIP patch: add parser location info to most expression node types

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group