Re: how to make PostgreSQL using "all" memory and chaching the DB completely there

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: "Christoph Anton Mitterer" <christoph(dot)anton(dot)mitterer(at)physik(dot)uni-muenchen(dot)de>, <pgsql-admin(at)postgresql(dot)org>
Cc: "Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com>
Subject: Re: how to make PostgreSQL using "all" memory and chaching the DB completely there
Date: 2011-07-21 15:06:45
Message-ID: 4E27FA35020000250003F64F@gw.wicourts.gov
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Christoph Anton Mitterer
<christoph(dot)anton(dot)mitterer(at)physik(dot)uni-muenchen(dot)de>
wrote:

> Well I'm still very unsure on how to configure many values...
> We've increased e.g. shared_buffers, temp_buffers, work_mem,
> maintenance_work_mem, max_stack_depth... and this greatly improved
> performance. But I can hardly judge to which values I should
> increase all these (and a few more).

Maybe the ellipses cover these, but wal_buffers and
checkpoint_segments should generally be adjusted, too. I almost
always need to tweak some of the costing factors, too; but
appropriate settings there depend not only on your hardware, but
also your schema, data, and application mix.

The best source of information on this that I know is Greg Smith's
"PostgreSQL 9.0 High Performance" book. (It also discusses older
versions, so don't let the "9.0" in the title put you off.) Some of
these settings are best tuned through an iterative process of
monitoring while making small adjustments.

http://www.postgresql.org/docs/books/

-Kevin

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message Kevin Grittner 2011-07-21 15:55:48 Re: vacuumdb question/problem
Previous Message David Ondrejik 2011-07-21 14:44:37 Re: vacuumdb question/problem