Re: Increase NUM_XLOGINSERT_LOCKS - Mailing list pgsql-hackers

From Japin Li
Subject Re: Increase NUM_XLOGINSERT_LOCKS
Date
Msg-id ME0P300MB04450E4E20132FF031B40A3BB6E02@ME0P300MB0445.AUSP300.PROD.OUTLOOK.COM
Whole thread Raw
In response to Re: Increase NUM_XLOGINSERT_LOCKS  (Yura Sokolov <y.sokolov@postgrespro.ru>)
List pgsql-hackers
On Thu, 23 Jan 2025 at 15:50, Yura Sokolov <y.sokolov@postgrespro.ru> wrote:
> 23.01.2025 08:41, wenhui qiu wrote:
>> HI Japin
>>       Thank you for you test ,It seems NUM_XLOGINSERT_LOCKS 64
>> is great , I think it doesn't need to grow much,What do you think?
>
> I agree: while 128 shows small benefit, it is not as big at the moment.
> Given there's other waiting issues (may) arise from increasing it, 64
> seems to be sweet spot.
>
> Probably in a future it could be increased more after other places
> will be optimized.
>

+1.
--
Regrads,
Japin Li



pgsql-hackers by date:

Previous
From: Japin Li
Date:
Subject: Re: [RFC] Lock-free XLog Reservation from WAL
Next
From: Aleksander Alekseev
Date:
Subject: Re: [PATCH] Add get_bytes() and set_bytes() functions