Postgres Pro
Downloads
Home   >   mailing lists

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

From David Rowley
Subject Re: Prefetch the next tuple's memory during seqscans
Date
Msg-id CAApHDvoLOKwbe-ObFB0tet7wu7bDpCC5Fv9J_CqTMPGgvRdEvQ@mail.gmail.com
Whole thread Raw
In response to Re: Prefetch the next tuple's memory during seqscans  (John Naylor <john.naylor@enterprisedb.com>)
Responses Re: Prefetch the next tuple's memory during seqscans
List pgsql-hackers
Tree view 
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?

My tests were all on AMD Zen 2. I'm keen to see what the results are
on intel hardware.

David

pgsql-hackers by date:

Previous
From: David Rowley
Date:
Subject: Re: Prefetch the next tuple's memory during seqscans
Next
From: Robert Haas
Date:
Subject: Re: fixing CREATEROLE