Re: Lock contention high

From: Michael Lewis <mlewis(at)entrata(dot)com>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: Ashkil Dighin <ashkildighin76(at)gmail(dot)com>, Pgsql Performance <pgsql-performance(at)lists(dot)postgresql(dot)org>
Subject: Re: Lock contention high
Date: 2021-10-26 00:38:40
Message-ID: CAHOFxGqQBX46a+v4RyV5BBVY4wQ6m6p_mDzPw+vXQ+2Yz+Gdcw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

On Mon, Oct 25, 2021, 5:36 PM Andres Freund <andres(at)anarazel(dot)de> wrote:
If your hot data set is actually larger than s_b, I'd recommend trying a
larger s_b. It's plausible that a good chunk of lock contention is from
that.

How much larger might you go? Any write ups on lock contention as it
relates to shared buffers? How impactful might huge pages (off, transparent
or on) be to the use of shared buffers and the related locking mechanism?

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Andres Freund 2021-10-26 00:43:23 Re: Lock contention high
Previous Message Andres Freund 2021-10-25 23:35:46 Re: Lock contention high