| From: | John Naylor <john(dot)naylor(at)enterprisedb(dot)com> |
|---|---|
| To: | David Rowley <dgrowleyml(at)gmail(dot)com> |
| Cc: | Aleksander Alekseev <aleksander(at)timescale(dot)com>, PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
| Subject: | Re: Prefetch the next tuple's memory during seqscans |
| Date: | 2022-11-23 01:35:06 |
| Message-ID: | CAFBsxsGOCBkuEobBU8FUdruhaO_wZWD0imTdUW_79R-1ownGCA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Nov 23, 2022 at 5:00 AM David Rowley <dgrowleyml(at)gmail(dot)com> wrote:
>
> On Thu, 3 Nov 2022 at 22:09, John Naylor <john(dot)naylor(at)enterprisedb(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2022-11-23 01:36:06 | Re: ssl tests aren't concurrency safe due to get_free_port() |
| Previous Message | Andres Freund | 2022-11-23 01:26:07 | Re: ssl tests aren't concurrency safe due to get_free_port() |