Re: I/O timigns don't include time for temp buffers

From: Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>
To: depesz(at)depesz(dot)com
Cc: PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: I/O timigns don't include time for temp buffers
Date: 2021-08-12 02:45:59
Message-ID: CAD21AoDvF=e7QxLgx5g52P-ES0gXdOX6b8dbVUPhuhxmxNcNNw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Wed, Aug 11, 2021 at 5:35 PM hubert depesz lubaczewski
<depesz(at)depesz(dot)com> wrote:
>
> On Tue, Aug 10, 2021 at 03:15:27PM +0900, Masahiko Sawada wrote:
> > > This shows that the Hash wrote 1100 temp buffers, but I/O timings didn't increase at all.
> > Yes, we don't collect the time spent reading and writing temp files.
>
> And this is the source of my concern.
>
> Not that we have this documented in one way or another, but why exactly
> aren't we taking temp buffers into timing? There are cases where it is
> the temp buffers IO that is using most of the time.

Yes. I agree that there is room for improvement there. It seems to me
that it's an improvement, not a bug. So it would be better to discuss
it on pgsql-hackers.

Regards,

--
Masahiko Sawada
EDB: https://www.enterprisedb.com/

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Emil Iggland 2021-08-12 06:47:56 Re: BUG #17141: SELECT LIMIT WITH TIES FOR UPDATE SKIP LOCKED returns wrong number of rows
Previous Message David Christensen 2021-08-11 21:39:00 Re: BUG #17141: SELECT LIMIT WITH TIES FOR UPDATE SKIP LOCKED returns wrong number of rows