Re: [PATCH v1 1/1] PostgreSQL Patch: AVX-Optimized ASCII Validation

From: John Naylor <johncnaylorls(at)gmail(dot)com>
To: "Pickett, Eshe N" <eshe(dot)n(dot)pickett(at)intel(dot)com>
Cc: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [PATCH v1 1/1] PostgreSQL Patch: AVX-Optimized ASCII Validation
Date: 2025-11-04 09:35:14
Message-ID: CANWCAZZnXjwMC=W5p5=rUuyoCDZWPa5qESx++7t+62XKAq899A@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Nov 4, 2025 at 2:45 PM Pickett, Eshe N <eshe(dot)n(dot)pickett(at)intel(dot)com> wrote:
> This patch series introduces Intel AVX2 and AVX-512 optimized ASCII validation
>
> for PostgreSQL's UTF-8 processing pipeline, providing significant performance
>
> improvements for text-heavy workloads through vectorized string validation.

We already use SSE2/Neon here, and and a good compiler can unroll 2
vectors to work on 32-bytes per loop iteration. Profiles of COPY FROM
should not show ASCII validation to be a large part of the profile
anymore. The bottlenecks are most likely elsewhere. I don't believe
this is worth it.

--
John Naylor
Amazon Web Services

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Chao Li 2025-11-04 09:40:19 Re: [PATCH] Add pretty formatting to pg_get_triggerdef
Previous Message Mats Kindahl 2025-11-04 09:31:31 Re: Coccinelle for PostgreSQL development [1/N]: coccicheck.py