Postgres Pro
Downloads
Home   >   mailing lists

Re: Prefetch the next tuple's memory during seqscans - Mailing list pgsql-hackers

From John Naylor
Subject Re: Prefetch the next tuple's memory during seqscans
Date
Msg-id CAFBsxsGOCBkuEobBU8FUdruhaO_wZWD0imTdUW_79R-1ownGCA@mail.gmail.com
Whole thread Raw
In response to Re: Prefetch the next tuple's memory during seqscans  (David Rowley <dgrowleyml@gmail.com>)
List pgsql-hackers
Tree view

On Wed, Nov 23, 2022 at 5:00 AM David Rowley <dgrowleyml@gmail.com> wrote:
>
> On Thu, 3 Nov 2022 at 22:09, John Naylor <john.naylor@enterprisedb.com> wrote:
> > I tried a similar test, but with text fields of random length, and there is improvement here:
>
> Thank you for testing that. Can you share which CPU this was on?

That was an Intel Core i7-10750H

--
John Naylor
EDB: http://www.enterprisedb.com

pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: ssl tests aren't concurrency safe due to get_free_port()
Next
From: Tom Lane
Date:
Subject: Re: ssl tests aren't concurrency safe due to get_free_port()