public inbox for [email protected]
help / color / mirror / Atom feedFrom: Bruce Momjian <[email protected]>
To: John Naylor <[email protected]>
Cc: PostgreSQL-development <[email protected]>
Subject: Re: PG 16 draft release notes ready
Date: Wed, 24 May 2023 00:19:40 -0400
Message-ID: <[email protected]> (raw)
In-Reply-To: <CAFBsxsEPg8L2MmGqavc8JByC=WF_Mnkhn-KKnFPkcqh0hydung@mail.gmail.com>
References: <[email protected]>
<CAFBsxsEuAx4_nq=200u=70S5r83C2hzO-a9+c6YXTCbOFeDAfw@mail.gmail.com>
<[email protected]>
<CAFBsxsEPg8L2MmGqavc8JByC=WF_Mnkhn-KKnFPkcqh0hydung@mail.gmail.com>
On Tue, May 23, 2023 at 12:14:04PM +0700, John Naylor wrote:
> On Tue, May 23, 2023 at 11:26 AM Bruce Momjian <[email protected]> wrote:
> >
> > On Tue, May 23, 2023 at 09:58:30AM +0700, John Naylor wrote:
> > > > 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".
> >
> > Okay, I kept "vector". I don't think moving them into performance makes
> > sense because there I don't think this would impact user behavior or
> > choice, and it can't be controlled.
>
> Well, these two items were only committed because of measurable speed
> increases, and have zero effect on how developers work with "source code", so
> that's a category error.
>
> Whether they rise to the significance of warranting inclusion in release notes
> is debatable.
Okay, let's dissect this. First, I am excited about these features
because I think they show innovation, particularly for high scaling, so
I want to highlight this.
Second, you might be correct that the section is wrong. I thought of
CPU instructions as something tied to the compiler, so part of the build
process or source code, but the point we should be make is that we have
these acceleration, not how it is implemented. We can move the entire
group to the "General Performance" section, or we can split it out:
Keep in source code:
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)
move to General Performance:
Allow xid/subxid searches to use vector operations (Nathan Bossart)
Allow ASCII string detection to use vector operations (John Naylor)
and add these to data types:
Allow JSON string parsing to use vector operations (John Naylor)
Allow array searches to use vector operations (John Naylor)
--
Bruce Momjian <[email protected]> https://momjian.us
EDB https://enterprisedb.com
Only you can decide what is important to you.
view thread (63+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected]
Subject: Re: PG 16 draft release notes ready
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox