Re: Vectored IO in XLogWrite()

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Melih Mutlu <m(dot)melihmutlu(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Vectored IO in XLogWrite()
Date: 2024-12-11 00:41:11
Message-ID: Z1jfp53VOfb7Wz_F@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Aug 08, 2024 at 01:25:47PM -0400, Robert Haas wrote:
> I wondered whether the regression tests actually hit the iovcnt == 2
> case, and it turns out that they do, rather frequently actually.
> Making that case a FATAL causes ~260 regression test failure. However,
> on larger systems, we'll often end up with wal_segment_size=16MB and
> wal_buffers=16MB and then it seems like we don't hit the iovcnt==2
> case. Which I guess just reinforces the point that this is
> theoretically better but practically not much different.
>
> Any other votes on what to do here?

Perhaps some micro-benchmarking to prove that the patch shows benefits
when this code path is taken alone? I could fall behind that.

I'd also document the maths of the patch a bit more, it is always kind
of hard to figure out if iovec is set up right or not. And the
formulas used in the patch look magical.
--
Michael

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message David Rowley 2024-12-11 00:49:42 Re: Add ExprState hashing for GROUP BY and hashed SubPlans
Previous Message Michael Paquier 2024-12-11 00:34:40 Re: Serverside SNI support in libpq