Re: pgcon unconference / impact of block size on performance

From: Tomas Vondra <tomas(dot)vondra(at)enterprisedb(dot)com>
To: Roberto Mello <roberto(dot)mello(at)gmail(dot)com>
Cc: Bruce Momjian <bruce(at)momjian(dot)us>, "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: pgcon unconference / impact of block size on performance
Date: 2022-06-05 09:51:32
Message-ID: 719e1856-8eb3-905c-1739-3b1b6c6f5858@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 6/5/22 02:21, Roberto Mello wrote:
> On Sat, Jun 4, 2022 at 5:23 PM Tomas Vondra
> <tomas(dot)vondra(at)enterprisedb(dot)com <mailto: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.
>
>
> Thanks for sharing this Thomas.
>
> We’ve been doing similar tests with different storage classes in
> kubernetes clusters. 
>

Can you share some of the results? Might be interesting, particularly if
you use network-attached storage (like EBS, etc.).

regards

--
Tomas Vondra
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Anton A. Melnikov 2022-06-05 10:38:01 Re: [PATCH] Fix pg_upgrade test from v10
Previous Message Michael Paquier 2022-06-05 09:19:33 Re: [v15 beta] pg_upgrade failed if earlier executed with -c switch