Re: Now I am back, next thing. Final PGS tuning.

From: "Massa, Harald Armin" <chef(at)ghum(dot)de>
To: Bill Moran <wmoran(at)potentialtech(dot)com>
Cc: Jennifer Trey <jennifer(dot)trey(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org
Subject: Re: Now I am back, next thing. Final PGS tuning.
Date: 2009-04-08 14:38:24
Message-ID: e3e180dc0904080738v470cf8cg3b72ff67a1bb683c@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Bill, Jennifer,

> *shared_buffers = 1024 # min 128kB or max_connections*16kB ## Also to
> low.
> > Right? I've got 3GB to work with!*
>
> Assuming that's equating to 1G, then the value is about right. Common
> best practice is to set this value to 1/4 - 1/3 of the memory available
> for PostgreSQL. You're saying you'll have ~3G for PG, so 1G is about
> right to start with.
>
>
"documenting" that for the wiki is still on my backlog; so, here:

shared_buffers of PostgreSQL on Windows != shared_buffers of PostgreSQL on
Unix

My experience is that raising shared_memory on Windows above minimum+~20% is
not helping performance; it's more effective to have that memory at Windows
for caching. (at least up to server 2003)

Harald

--
GHUM Harald Massa
persuadere et programmare
Harald Armin Massa
Spielberger Straße 49
70435 Stuttgart
0173/9409607
no fx, no carrier pigeon
-
LASIK good, steroids bad?

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Jennifer Trey 2009-04-08 14:40:34 Re: Now I am back, next thing. Final PGS tuning.
Previous Message Bill Moran 2009-04-08 14:23:53 Re: Now I am back, next thing. Final PGS tuning.