bug#31138: Native json slower than json.el

[Eli Zaretskii]

> Cc: sebastien@chapu.is, 31138@debbugs.gnu.org
> From: Dmitry Gutov <dgutov@yandex.ru>
> Date: Tue, 16 Apr 2019 04:36:43 +0300
> 
> On 26.03.2019 18:14, Eli Zaretskii wrote:
> > I think we should only consider this after we profile JSON parsing and
> > see which parts take the most processing time.
> 
> What is our next step here?
> 
> I have tried out the comparison (with and without code_convert_string) 
> on my own JSON data, and the results are similar: 6MB JSON is parsed in 
> ~0.48s by default, and in ~0.21s with that call removed.
> 
> The JSON parsing is not the biggest bottleneck in my particular case, 
> but it would be nice to speed it up anyway.
> 
> So what should we profile? The internals of code_convert_string?

The entire run of parsing a large JSON.  code_convert_string will be
part of the profile.