From: | John Naylor <john(dot)naylor(at)enterprisedb(dot)com> |
---|---|
To: | Bruce Momjian <bruce(at)momjian(dot)us> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: PG 16 draft release notes ready |
Date: | 2023-05-23 02:58:30 |
Message-ID: | CAFBsxsEuAx4_nq=200u=70S5r83C2hzO-a9+c6YXTCbOFeDAfw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi Bruce,
> Add support for SSE2 (Streaming SIMD Extensions 2) vector operations on
x86-64 architectures (John Naylor)
> Add support for Advanced SIMD (Single Instruction Multiple Data) (NEON)
instructions on ARM architectures (Nathan Bossart)
Nit: It's a bit odd that SIMD is spelled out in only the Arm entry, and
perhaps expanding the abbreviations can be left out.
> Allow arrays searches to use vector operations on x86-64 architectures
(John Naylor)
We can leave out the architecture here (see below). Typo: "array searches"
All the above seem appropriate for the "source code" section, but the
following entries might be better in the "performance" section:
> Allow ASCII string detection to use vector operations on x86-64
architectures (John Naylor)
> Allow JSON string processing to use vector operations on x86-64
architectures (John Naylor)
>
> ARM?
Arm as well. For anything using 16-byte vectors the two architectures are
equivalently supported. For all the applications, I would just say "vector"
or "SIMD".
And here maybe /processing/parsing/.
> Allow xid/subxid searches to use vector operations on x86-64
architectures (Nathan Bossart)
When moved to the performance section, it would be something like "improve
scalability when a large number of write transactions are in progress".
--
John Naylor
EDB: http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2023-05-23 04:26:23 | Re: PG 16 draft release notes ready |
Previous Message | Tom Lane | 2023-05-22 23:19:18 | Re: Add missing includes |