Re: speed up verifying UTF-8
John Naylor <john.naylor@enterprisedb.com>
From: John Naylor <john.naylor@enterprisedb.com>
To: Greg Stark <stark@mit.edu>
Cc: Heikki Linnakangas <hlinnaka@iki.fi>,
Amit Khandekar <amitdkhan.pg@gmail.com>, pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2021-06-03T15:33:21Z
Lists: 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
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Simplify coding style of is_valid_ascii()
- 6b41a1579bd3 16.0 landed
-
Apply auto-vectorization to the inner loop of numeric multiplication.
- 88709176236c 14.0 cited