Re: Make NUM_XLOGINSERT_LOCKS configurable

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: Make NUM_XLOGINSERT_LOCKS configurable
Дата
Msg-id 2345175.1704867237@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Re: Make NUM_XLOGINSERT_LOCKS configurable  (Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>)
Ответы Re: Make NUM_XLOGINSERT_LOCKS configurable  (Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>)
Список pgsql-hackers
Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com> writes:
> On Wed, Jan 10, 2024 at 10:00 AM Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> Maybe.  I bet just bumping up the constant by 2X or 4X or so would get
>> most of the win for far less work; it's not like adding a few more
>> LWLocks is expensive.  But we need some evidence about what to set it to.

> I previously made an attempt to improve WAL insertion performance with
> varying NUM_XLOGINSERT_LOCKS. IIRC, we will lose what we get by
> increasing insertion locks (reduction in WAL insertion lock
> acquisition time) to the CPU overhead of flushing the WAL in
> WaitXLogInsertionsToFinish as referred to by the following comment.

Very interesting --- this is at variance with what the OP said, so
we definitely need details about the test conditions in both cases.

> Unfortunately, I've lost the test results, I'll run them up again and
> come back.

Please.

            regards, tom lane



В списке pgsql-hackers по дате отправления:

Предыдущее
От: Bharath Rupireddy
Дата:
Сообщение: Re: Make NUM_XLOGINSERT_LOCKS configurable
Следующее
От: John Naylor
Дата:
Сообщение: Re: Add BF member koel-like indentation checks to SanityCheck CI