Re: Reduce ProcArrayLock contention

From: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
To: Simon Riggs <simon(at)2ndquadrant(dot)com>
Cc: Andres Freund <andres(at)anarazel(dot)de>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Reduce ProcArrayLock contention
Date: 2015-06-30 06:30:39
Message-ID: CAA4eK1Jcc=1o=Sc+QFt6K_6ROB13q-AXxGo9zmjSYbuBgGAcVw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Jun 30, 2015 at 11:53 AM, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
>
> On 30 June 2015 at 04:21, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> wrote:
>
>>
>> Now, I would like to briefly explain how allow-one-waker idea has
>> helped to improve the patch as not every body here was present
>> in that Un-conference.
>
>
> The same idea applies for marking commits in clog, for which I have been
sitting on a patch for a month or so and will post now I'm done travelling.
>

Sure and I think we might want to try something similar even
for XLogFlush where we use LWLockAcquireOrWait for
WALWriteLock, not sure how it will workout in that case as
I/O is involved, but I think it is worth trying.

With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Kapila 2015-06-30 06:34:57 Re: drop/truncate table sucks for large values of shared buffers
Previous Message Jeff Janes 2015-06-30 06:28:47 Re: LWLock deadlock and gdb advice