Re: pgcon unconference / impact of block size on performance

From: Roberto Mello <roberto(dot)mello(at)gmail(dot)com>
To: Tomas Vondra <tomas(dot)vondra(at)enterprisedb(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 00:21:07
Message-ID: CAKz==bLqmYt67Z8DRgw90t_Zqid3apHZQ3SGvOjDG3QLYcmi=A@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sat, Jun 4, 2022 at 5: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.

Thanks for sharing this Thomas.

We’ve been doing similar tests with different storage classes in kubernetes
clusters.

Roberto

>

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2022-06-05 00:24:25 Re: [v15 beta] pg_upgrade failed if earlier executed with -c switch
Previous Message Tomas Vondra 2022-06-04 23:22:48 pgcon unconference / impact of block size on performance