Re: Streamify more code paths

From: Xuneng Zhou <xunengzhou(at)gmail(dot)com>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: Andres Freund <andres(at)anarazel(dot)de>, pgsql-hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Nazir Bilal Yavuz <byavuz81(at)gmail(dot)com>
Subject: Re: Streamify more code paths
Date: 2026-03-13 02:39:52
Message-ID: CABPTF7XxdAA681duGKgWx-eLC1skR3giuebcw4+-0GkOVZm-pw@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Mar 13, 2026 at 9:50 AM Michael Paquier <michael(at)paquier(dot)xyz> wrote:
>
> On Thu, Mar 12, 2026 at 11:35:48PM +0800, Xuneng Zhou wrote:
> > Our io_time metric currently measures only read time and ignores write
> > I/O, which can be misleading. We now separate it into read_time and
> > write_time.
>
> I had a look at the pgstatindex part this morning, running my own test
> under conditions similar to 6c228755add8, and here's one extract with
> io_uring:
> pgstatindex (100k tuples) base=32938.2ms patch=83.3ms 395.60x ( 99.7%)
> (reads=2745->173, io_time=32932.09->59.75ms)

This result looks great!

> There was one issue with a declaration put in the middle of the code,
> that I have fixed. This one is now done, remains 3 pieces to
> evaluate.

Thanks for fixing this and for taking the time to review and test the patches.

--
Best,
Xuneng

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Sami Imseih 2026-03-13 02:52:10 Re: Add missing stats_reset column to pg_statio_all_sequences view
Previous Message Manni Wood 2026-03-13 02:39:38 Re: Speed up COPY FROM text/CSV parsing using SIMD