Re: [PERFORM] Quad processor options

From: Halford Dace <hal(at)stowe(dot)co(dot)za>
To: pgsql-admin(at)postgresql(dot)org
Subject: Re: [PERFORM] Quad processor options
Date: 2004-05-12 10:27:18
Message-ID: F1FE4396-A3FE-11D8-9A93-000A95A9B750@stowe.co.za
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin pgsql-performance


On 12 May 2004, at 12:17 PM, Manfred Koizar wrote:

> On Tue, 11 May 2004 15:46:25 -0700, Paul Tuckfield <paul(at)tuckfield(dot)com>
> wrote:
>
>> - I'll bet you have a low value for shared buffers, like 10000. On
>> your 3G system
>> you should ramp up the value to at least 1G (125000 8k buffers)
>
> In most cases this is almost the worst thing you can do. The only
> thing
> even worse would be setting it to 1.5 G.
>
> Postgres is just happy with a moderate shared_buffers setting. We
> usually recommend something like 10000. You could try 20000, but don't
> increase it beyond that without strong evidence that it helps in your
> particular case.
>
> This has been discussed several times here, on -hackers and on
> -general.
> Search the archives for more information.

We have definitely found this to be true here. We have some fairly
complex queries running on a rather underpowered box (beautiful but
steam-driven old Silicon Graphics Challenge DM). We ended up using a
very slight increase to shared buffers, but gaining ENORMOUSLY through
proper optimisation of queries, appropriate indices and the use of
optimizer-bludgeons like "SET ENABLE_SEQSCAN = OFF"

Hal

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message Daniel Kalchev 2004-05-12 11:08:04 Re: [PERFORM] Quad processor options
Previous Message Manfred Koizar 2004-05-12 10:17:27 Re: [PERFORM] Quad processor options

Browse pgsql-performance by date

  From Date Subject
Next Message scott.marlowe 2004-05-12 13:44:37 Re: [PERFORM] Quad processor options
Previous Message Manfred Koizar 2004-05-12 10:17:27 Re: [PERFORM] Quad processor options