Re: Speed up JSON escape processing with SIMD plus other optimisations
Andrew Dunstan <andrew@dunslane.net>
From: Andrew Dunstan <andrew@dunslane.net>
To: Melih Mutlu <m.melihmutlu@gmail.com>, David Rowley <dgrowleyml@gmail.com>
Cc: PostgreSQL Developers <pgsql-hackers@lists.postgresql.org>
Date: 2024-06-11T12:31:23Z
Lists: pgsql-hackers
On 2024-06-11 Tu 08:08, Melih Mutlu wrote:
> Hi David,
>
> Thanks for the patch.
>
> In 0001 patch, I see that there are some escape_json() calls with
> NUL-terminated strings and gets the length by calling strlen(), like
> below:
>
> - escape_json(&buf, "timestamp");
> + escape_json(&buf, "timestamp", strlen("timestamp"));
>
>
> Wouldn't using escape_json_cstring() be better instead? IIUC there
> isn't much difference between escape_json() and escape_json_cstring(),
> right? We would avoid strlen() with escape_json_cstring().
>
>
or maybe use sizeof("timestamp") - 1
cheers
andrew
--
Andrew Dunstan
EDB:https://www.enterprisedb.com
Commits
-
Optimize JSON escaping using SIMD
- ca6fde92258a 18.0 landed
-
Optimize escaping of JSON strings
- 17a5871d9d58 18.0 landed