Re: speed up verifying UTF-8 - Mailing list pgsql-hackers

From John Naylor
Subject Re: speed up verifying UTF-8
Date
Msg-id CAFBsxsH1kPY+us49gXVf6zv6bLPC5NHm1f1VW+UdpVH8i+JD4w@mail.gmail.com
Whole thread Raw
In response to Re: speed up verifying UTF-8  (Greg Stark <stark@mit.edu>)
Responses Re: speed up verifying UTF-8  (John Naylor <john.naylor@enterprisedb.com>)
List pgsql-hackers

On Thu, Jun 3, 2021 at 10:42 AM Greg Stark <stark@mit.edu> wrote:
>
> I haven't looked at the surrounding code. Are we processing all the
> COPY data in one long stream or processing each field individually? 

It happens on 64kB chunks.

> If
> we're processing much more than 128 bits and happy to detect NUL
> errors only at the end after wasting some work then you could hoist
> that has_zero check entirely out of the loop (removing the branch
> though it's probably a correctly predicted branch anyways).
>
> Do something like:
>
> zero_accumulator = zero_accumulator & next_chunk
>
> in the loop and then only at the very end check for zeros in that.

That's the approach taken in the SSE4 patch, and in fact that's the logical way to do it there. I hadn't considered doing it that way in the pure C case, but I think it's worth trying.

--
John Naylor
EDB: http://www.enterprisedb.com

pgsql-hackers by date:

Previous
From: Nitin Jadhav
Date:
Subject: Re: Multi-Column List Partitioning
Next
From: Andrey Lepikhov
Date:
Subject: Re: Asynchronous Append on postgres_fdw nodes.