Re: Reducing ClogControlLock contention

From: Simon Riggs <simon(at)2ndQuadrant(dot)com>
To: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
Cc: Simon Riggs <simon(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Reducing ClogControlLock contention
Date: 2015-07-01 10:15:40
Message-ID: CANP8+jLFNZ2m+k0MXa3pt19H5UBDkaQpNPqUhRp9Sd35p7McgA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 1 July 2015 at 11:11, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> wrote:

> On Wed, Jul 1, 2015 at 1:38 PM, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
> >
> > On 1 July 2015 at 09:00, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> wrote:
> >>
> >>
> >> I think it will be better to partition it or use it in some other way
> to avoid
> >> two concurrent writers block at it, however if you want to first see the
> >> test results with this, then that is also okay.
> >
> >
> > Many updates would be on same page, so partitioning it would need to be
> at least 4-way to be worth doing. Maybe we could stripe into 512 bye pages.
> >
>
> Sure, it makes sense to try that way, once you have that ready, I can
> try this out along with ProcArrayLock patch to see the impact.
>

Seems sensible to measure what the new point of contention is with both
before doing anything further.

--
Simon Riggs http://www.2ndQuadrant.com/
<http://www.2ndquadrant.com/>
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Simon Riggs 2015-07-01 10:19:40 Re: Reducing ClogControlLock contention
Previous Message Andres Freund 2015-07-01 10:14:02 Re: Reducing ClogControlLock contention