On Tue, May 23, 2023 at 11:26 AM Bruce Momjian <
bruce@momjian.us> 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.
> > > 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".
>
> Uh, again, see above, this does not impact user behavior or choices.
So that turns a scalability improvement into "source code"?
> I assume this is x86-64-only.
Au contraire, I said "For anything using 16-byte vectors the two architectures are equivalently supported". It's not clear from looking at individual commit messages, that's why I piped in to help.
--
John Naylor
EDB:
http://www.enterprisedb.com