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 CAGTBQpaFon0fKMk6ikdpAf0jKfHrNh+caNunKnJ30jozX2K17w@mail.gmail.com
Whole thread Raw
In response to Re: shared_buffers/effective_cache_size on 96GB server  (Strahinja Kustudić <strahinjak@nordeus.com>)
List pgsql-performance
On Wed, Oct 10, 2012 at 5:12 PM, Strahinja Kustudić
<strahinjak@nordeus.com> wrote:
> @Claudio So you are basically saying that if I have set effective_cache_size
> to 10GB and I have 10 concurrent processes which are using 10 different
> indices which are for example 2GB, it would be better to set the
> effective_cache size to 1GB? Since if I leave it at 10GB each running
> process query planner will think the whole index is in cache and that won't
> be true? Did I get that right?

Yep. You might get away with setting 2GB, if you're willing to bet
there won't be 100% concurrency. But the safest setting would be 1G.


pgsql-performance by date:

Previous
From: Strahinja Kustudić
Date:
Subject: Re: shared_buffers/effective_cache_size on 96GB server
Next
From: Bruce Momjian
Date:
Subject: Re: shared_buffers/effective_cache_size on 96GB server