Re: Clock sweep not caching enough B-Tree leaf pages?

From: Claudio Freire <klaussfreire(at)gmail(dot)com>
To: David G Johnston <david(dot)g(dot)johnston(at)gmail(dot)com>
Cc: PostgreSQL-Dev <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Clock sweep not caching enough B-Tree leaf pages?
Date: 2014-04-21 23:09:20
Message-ID: CAGTBQpbgh6qwBjY2SWTM76SewMZ=EGs54baPXhjyK3=ZfV7mAA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Apr 21, 2014 at 8:07 PM, David G Johnston
<david(dot)g(dot)johnston(at)gmail(dot)com> wrote:
> Jim Nasby-2 wrote
>>> I feel that if there is no memory pressure, frankly it doesnt matter much
>>> about what gets out and what not. The case I am specifically targeting is
>>> when the clocksweep gets to move about a lot i.e. high memory pressure
>>> workloads. Of course, I may be totally wrong here.
>>
>> Well, there's either memory pressure or there isn't. If there isn't then
>> it's all moot *because we're not evicting anything*.
>
> The trade-off I'm seeing here is between measuring when there is no memory
> pressure - and thus eating at performance while not actually evicting
> buffers - and not measuring but then encountering memory pressure and not
> having a clue as to what should be evicted.

I believe that for the intended use discussed in this thread, a
compile-time switch would be more than enough control, and it would
avoid that tradeoff.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2014-04-21 23:20:24 Re: Removing dependency to wsock32.lib when compiling code on WIndows
Previous Message David G Johnston 2014-04-21 23:07:16 Re: Clock sweep not caching enough B-Tree leaf pages?