[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#31138: Native json slower than json.el
|
From: |
Dmitry Gutov |
|
Subject: |
bug#31138: Native json slower than json.el |
|
Date: |
Tue, 16 Apr 2019 04:36:43 +0300 |
|
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1 |
Hi Eli,
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?
- bug#31138: Native json slower than json.el,
Dmitry Gutov <=
- bug#31138: Native json slower than json.el, Eli Zaretskii, 2019/04/15
- bug#31138: Native json slower than json.el, Dmitry Gutov, 2019/04/16
- bug#31138: Native json slower than json.el, Eli Zaretskii, 2019/04/16
- bug#31138: Native json slower than json.el, Dmitry Gutov, 2019/04/16
- bug#31138: Native json slower than json.el, Eli Zaretskii, 2019/04/16
- bug#31138: Native json slower than json.el, Dmitry Gutov, 2019/04/16
- bug#31138: Native json slower than json.el, Eli Zaretskii, 2019/04/16
- bug#31138: Native json slower than json.el, Eli Zaretskii, 2019/04/21
- bug#31138: Native json slower than json.el, Dmitry Gutov, 2019/04/21
- bug#31138: Native json slower than json.el, Eli Zaretskii, 2019/04/21