GNU bug report logs -
#20154
25.0.50; json-encode-string is too slow for large strings
Previous Next
Reported by: Dmitry Gutov <dgutov <at> yandex.ru>
Date: Fri, 20 Mar 2015 14:27:01 UTC
Severity: normal
Found in version 25.0.50
Done: Dmitry Gutov <dgutov <at> yandex.ru>
Bug is archived. No further changes may be made.
Full log
Message #23 received at 20154 <at> debbugs.gnu.org (full text, mbox):
On 03/20/2015 06:02 PM, Eli Zaretskii wrote:
> I have other things on my plate while I read email. If my advice
> bothers you, I can shut up in the future.
Very well. Please continue with the advice.
> I suggest to rewrite json-encode-char, it does a lot of unnecessary
> stuff, starting with the call to encode-char (which was needed in
> Emacs 22 and before, but no more). The call to rassoc is also
> redundant, since you already have that covered in your regexp.
Yes, I thought about that, but as the number of calls to
`json-encode-char' must have decreased by 10 in the new version (only
each 10th character needs to be encoded), and the runtime only decreased
by 3 (or by 2, in a different example I have), the total improvement
can't be dramatic enough even if `json-encode-char' is lightning-fast.
This bug report was last modified 10 years and 38 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.