Re: [RFC] Lock-free XLog Reservation from WAL

From: "Zhou, Zhiguo" <zhiguo(dot)zhou(at)intel(dot)com>
To: Yura Sokolov <y(dot)sokolov(at)postgrespro(dot)ru>
Cc: wenhui qiu <qiuwenhuifx(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [RFC] Lock-free XLog Reservation from WAL
Date: 2025-01-17 14:00:35
Message-ID: 15d7595b-bb49-4205-bf8a-b3af2a026dde@intel.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 1/16/2025 10:00 PM, Yura Sokolov wrote:
>
> Good day, Zhiguo.
>
> Excuse me, I feel sneaky a bit, but I've started another thread just
> about increase of NUM_XLOGINSERT_LOCK, because I can measure its effect
> even on my working notebook (it is another one: Ryzen 5825U limited to
> @2GHz).
>
> http://postgr.es/m/flat/3b11fdc2-9793-403d-
> b3d4-67ff9a00d447%40postgrespro.ru
>
> -----
>
> regards
> Yura Sokolov aka funny-falcon
>
>

Good day, Yura!

Thank you for keeping me informed. I appreciate your proactive approach
and understand the importance of exploring different angles for
optimization. Your patch is indeed fundamental to our ongoing work on
the lock-free xlog reservation, and I'm eager to see how it can further
enhance our efforts.

I will proceed to test the performance impact of your latest patch when
combined with the lock-free xlog reservation patch. This will help us
determine if there's potential for additional optimization.
Concurrently, with your permission, I'll try to refine the
hash-table-based implementation for your further review. WDYT?

Regards,
Zhiguo

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2025-01-17 14:16:08 Re: Re: proposal: schema variables
Previous Message Fujii Masao 2025-01-17 13:51:49 Re: ecpg command does not warn COPY ... FROM STDIN;