Re: shared_buffers/effective_cache_size on 96GB server

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Claudio Freire <klaussfreire(at)gmail(dot)com>
Cc: Julien Cigar <jcigar(at)ulb(dot)ac(dot)be>, pgsql-performance(at)postgresql(dot)org
Subject: Re: shared_buffers/effective_cache_size on 96GB server
Date: 2012-10-10 17:56:39
Message-ID: 20121010175639.GH11892@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

On Wed, Oct 10, 2012 at 02:05:20PM -0300, Claudio Freire wrote:
> On Wed, Oct 10, 2012 at 1:10 PM, Bruce Momjian <bruce(at)momjian(dot)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

It is true that the estimate assumes a single session is using all the
cache, but I think that is based on the assumion is that there is a
major overlap between the cache needs of multiple sessions.

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ It's impossible for everything to be true. +

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message Claudio Freire 2012-10-10 18:08:00 Re: Hyperthreading (was: Two identical systems, radically different performance)
Previous Message Craig James 2012-10-10 17:28:08 Re: Hyperthreading (was: Two identical systems, radically different performance)