Re: pgcon unconference / impact of block size on performance

From: Merlin Moncure <mmoncure(at)gmail(dot)com>
To: Tomas Vondra <tomas(dot)vondra(at)enterprisedb(dot)com>
Cc: "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Bruce Momjian <bruce(at)momjian(dot)us>
Subject: Re: pgcon unconference / impact of block size on performance
Date: 2022-06-13 15:42:31
Message-ID: CAHyXU0zaPTQF3dceu9eE8TgJy=nNniPwZyryOJiFJbydkDRZ3A@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sat, Jun 4, 2022 at 6:23 PM Tomas Vondra <tomas(dot)vondra(at)enterprisedb(dot)com>
wrote:

> Hi,
>
> At on of the pgcon unconference sessions a couple days ago, I presented
> a bunch of benchmark results comparing performance with different
> data/WAL block size. Most of the OLTP results showed significant gains
> (up to 50%) with smaller (4k) data pages.
>

Wow. Random numbers are fantastic, Significant reduction in sequential
throughput is a little painful though, I see 40% reduction in some cases if
I'm reading that right. Any thoughts on why that's the case? Are there
mitigations possible?

merlin

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2022-06-13 16:01:08 Re: pltcl crash on recent macOS
Previous Message Robert Haas 2022-06-13 15:01:05 Re: better page-level checksums