| From: | Japin Li <japinli(at)hotmail(dot)com> |
|---|---|
| To: | Yura Sokolov <y(dot)sokolov(at)postgrespro(dot)ru> |
| Cc: | wenhui qiu <qiuwenhuifx(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org>, "Zhou, Zhiguo" <zhiguo(dot)zhou(at)intel(dot)com> |
| Subject: | Re: Increase NUM_XLOGINSERT_LOCKS |
| Date: | 2025-01-23 13:45:17 |
| Message-ID: | ME0P300MB04450E4E20132FF031B40A3BB6E02@ME0P300MB0445.AUSP300.PROD.OUTLOOK.COM |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, 23 Jan 2025 at 15:50, Yura Sokolov <y(dot)sokolov(at)postgrespro(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Laurenz Albe | 2025-01-23 13:52:03 | Re: doc: explain pgstatindex fragmentation |
| Previous Message | Japin Li | 2025-01-23 13:44:28 | Re: [RFC] Lock-free XLog Reservation from WAL |