Re: shared_buffers/effective_cache_size on 96GB server

From: Claudio Freire <klaussfreire(at)gmail(dot)com>
To: Jeff Janes <jeff(dot)janes(at)gmail(dot)com>
Cc: Strahinja Kustudić <strahinjak(at)nordeus(dot)com>, pgsql-performance(at)postgresql(dot)org
Subject: Re: shared_buffers/effective_cache_size on 96GB server
Date: 2012-10-18 20:43:08
Message-ID: CAGTBQpaPx-Q1S5NPgCQpgabmTJYCGqWJ+qN++-v=BKo+namy=w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

On Thu, Oct 18, 2012 at 4:23 PM, Jeff Janes <jeff(dot)janes(at)gmail(dot)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 is the size of the table, not the index, which is primarily of
> concern. However, that mostly factors into how postgres uses
> effective_cache_size, not how you set it.

You're right, I just noticed that a few minutes ago (talk about telepathy).

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message Scott Marlowe 2012-10-18 22:06:24 Re: shared_buffers/effective_cache_size on 96GB server
Previous Message Jeff Janes 2012-10-18 19:50:32 Re: shared_buffers/effective_cache_size on 96GB server