From: | Andres Freund <andres(at)2ndquadrant(dot)com> |
---|---|
To: | Thom Brown <thom(at)linux(dot)com> |
Cc: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Scaling shared buffer eviction |
Date: | 2014-11-11 09:30:55 |
Message-ID: | 20141111093055.GC18565@alap3.anarazel.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 2014-11-11 09:29:22 +0000, Thom Brown wrote:
> On 26 September 2014 12:40, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> wrote:
>
> > On Tue, Sep 23, 2014 at 10:31 AM, Robert Haas <robertmhaas(at)gmail(dot)com>
> > wrote:
> > >
> > > But this gets at another point: the way we're benchmarking this right
> > > now, we're really conflating the effects of three different things:
> > >
> > > 1. Changing the locking regimen around the freelist and clocksweep.
> > > 2. Adding a bgreclaimer process.
> > > 3. Raising the number of buffer locking partitions.
> >
> > First of all thanks for committing part-1 of this changes and it
> > seems you are planing to commit part-3 based on results of tests
> > which Andres is planing to do and for remaining part (part-2), today
> >
>
> Were parts 2 and 3 committed in the end?
3 was committed. 2 wasn't because it's not yet clear whether how
beneficial it is generally.
Greetings,
Andres Freund
--
Andres Freund http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Etsuro Fujita | 2014-11-11 09:45:38 | Re: postgres_fdw behaves oddly |
Previous Message | Thom Brown | 2014-11-11 09:29:22 | Re: Scaling shared buffer eviction |