From: Ron Mayer <rm_pg@cheapcomplexdevices.com>
To: Manfred Koizar <mkoi-pg@aon.at>
Cc: Pallav Kalva <pkalva@deg.cc>
Cc: pgsql-performance@postgresql.org
Subject: Re: Setting Shared Buffers , Effective Cache, Sort Mem
Date: Fri, 23 Apr 2004 15:10:20 -0700 (PDT)
Message-ID: <Pine.LNX.4.58.0404231506310.5473@one> (raw)
In-Reply-To: <kt1j805pi254lk614038qaq92c7qs64egv@email.aon.at>
References: <4088062E.2050901@deg.cc>
<ubig80lo5itco1o393hlu43ijsqppskgbr@email.aon.at>
<4089261A.9070700@deg.cc>
<kt1j805pi254lk614038qaq92c7qs64egv@email.aon.at>
On Fri, 23 Apr 2004, Manfred Koizar wrote:
>
> Setting shared_buffers to half your available memory is the worst thing
> you can do. You would end up caching exactly the same set of blocks in
> the internal buffers and in the OS cache, thus effectively making one of
> the caches useless.
One minor detail... You wouldn't really cache the _exact_ same blocks
because cache-hits in shared-buffers (on the most frequently accessed
pages) would let the OS cache some other pages in it's cache.
But in my experience Manfred's right that there's no benefit and
some penalty to making shared_buffers so large it takes a significant
piece away from the OS's caching.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: rm_pg@cheapcomplexdevices.com, mkoi-pg@aon.at, pkalva@deg.cc
Subject: Re: Setting Shared Buffers , Effective Cache, Sort Mem
In-Reply-To: <Pine.LNX.4.58.0404231506310.5473@one>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox