Re: shared_buffers/effective_cache_size on 96GB server - Mailing list pgsql-performance

From Claudio Freire
Subject Re: shared_buffers/effective_cache_size on 96GB server
Date
Msg-id CAGTBQpZ0E2xyAeNZy6a4uyhzyfhSNMv3TRDeLWdeT16RYYMPOg@mail.gmail.com
Whole thread Raw
In response to Re: shared_buffers/effective_cache_size on 96GB server  (Bruce Momjian <bruce@momjian.us>)
Responses Re: shared_buffers/effective_cache_size on 96GB server  (Bruce Momjian <bruce@momjian.us>)
Re: shared_buffers/effective_cache_size on 96GB server  (Shaun Thomas <sthomas@optionshouse.com>)
List pgsql-performance
On Wed, Oct 10, 2012 at 1:10 PM, Bruce Momjian <bruce@momjian.us> wrote:
>> >shared_buffers = 10GB
>>
>> Generally going over 4GB for shared_buffers doesn't help.. some of
>> the overhead of bgwriter and checkpoints is more or less linear in
>> the size of shared_buffers ..
>>
>> >effective_cache_size = 90GB
>>
>> effective_cache_size should be ~75% of the RAM (if it's a dedicated server)
>
> Why guess?  Use 'free' to tell you the kernel cache size:
>
>         http://momjian.us/main/blogs/pgblog/2012.html#May_4_2012

Why does nobody every mention that concurrent access has to be taken
into account?

Ie: if I expect concurrent access to 10 really big indices, I'll set
effective_cache_size = free ram / 10


pgsql-performance by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: shared_buffers/effective_cache_size on 96GB server
Next
From: Franck Routier
Date:
Subject: Drawbacks of create index where is not null ?