Re: Batching page logging during B-tree build

From: Andrey Borodin <x4mmm(at)yandex-team(dot)ru>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: Peter Geoghegan <pg(at)bowt(dot)ie>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Heikki Linnakangas <hlinnaka(at)iki(dot)fi>
Subject: Re: Batching page logging during B-tree build
Date: 2020-10-10 16:00:07
Message-ID: AC84F779-A79D-417A-AA14-3C7FF2CEDE79@yandex-team.ru
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> 23 сент. 2020 г., в 23:29, Andres Freund <andres(at)anarazel(dot)de> написал(а):
>
> Hi,
>
> On 2020-09-23 11:19:18 -0700, Peter Geoghegan wrote:
>> On Fri, Sep 18, 2020 at 8:39 AM Andrey M. Borodin <x4mmm(at)yandex-team(dot)ru> wrote:
>>> Here is PoC with porting that same routine to B-tree. It allows to build B-trees ~10% faster on my machine.
>
> I wonder what the effect of logging WAL records as huge as this (~256kb)
> is on concurrent sessions. I think it's possible that logging 32 pages
> at once would cause latency increases for concurrent OLTP-ish
> writes. And that a smaller batch size would reduce that, while still
> providing most of the speedup.

Indeed, on my machine performance is indistinguishable between batches of 8, 16 and 32 pages, while still observable (~3...8%) with 8 against 4.

Best regards, Andrey Borodin,

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2020-10-10 16:14:18 Re: Make LANGUAGE SQL the default
Previous Message Juan José Santamaría Flecha 2020-10-10 14:29:38 Re: BUG #15858: could not stat file - over 4GB