17.01.2025 17:00, Zhou, Zhiguo пишет:
>
>
> 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?
Certainly.
And I will sent my version of 64bit operations on hash-table entries...
tomorrow.
Today is 3am at the moment...
I was doing "removal of WALBufMappingLock" [1]
and I want to sleep a lot...
[1]
https://postgr.es/m/flat/39b39e7a-41b4-4f34-b3f5-db735e74a723%40postgrespro.ru
-----
regards
Yura Sokolov aka funny-falcon
