unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: emacs-devel@gnu.org, yyoncho@gmail.com, joaotavora@gmail.com
Subject: Re: Speedup of functions to en/decode UTF-8 text
Date: Sat, 23 Nov 2019 20:49:46 +0200	[thread overview]
Message-ID: <83imnatol1.fsf@gnu.org> (raw)
In-Reply-To: <68de517e-8ba3-4bc5-985d-aeb894595658@yandex.ru> (message from Dmitry Gutov on Sat, 23 Nov 2019 20:42:09 +0200)

> Cc: emacs-devel@gnu.org
> From: Dmitry Gutov <dgutov@yandex.ru>
> Date: Sat, 23 Nov 2019 20:42:09 +0200
> 
> On 23.11.2019 11:37, Eli Zaretskii wrote:
> > I've made some changes in the functions that encode and decode UTF-8
> > text in an optimized fashion.  This is expected to speed up JSON
> > handling.  Some preliminary benchmarking of the decoding function
> > indicates speed improvements starting at modest 30-40%, and sometimes
> > much higher -- tenfold or more.  I'm not sure how this will fare in
> > the real-life handling of JSON objects
> 
> This is great. But were those 30-40% improvements in tests with strings 
> or JSON decoding?

With JSON decoding.  But I have a very small sample of that.

> I tested two old examples, and the difference is <10% (like 0.78s down 
> to 0.73s in the best case). Which is still welcome, of course.

As long as it's faster, I'm okay ;-)

Thanks for testing.



  reply	other threads:[~2019-11-23 18:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-23  9:37 Speedup of functions to en/decode UTF-8 text Eli Zaretskii
2019-11-23 10:43 ` João Távora
2019-11-23 10:48   ` Eli Zaretskii
2019-11-23 15:27 ` Stefan Monnier
2019-11-23 18:42 ` Dmitry Gutov
2019-11-23 18:49   ` Eli Zaretskii [this message]
     [not found] ` <CACCVLQWT8msiij50wSvzbCBwvEeh9jnXGsGA5xxGnY5DEOvvYw@mail.gmail.com>
2019-11-24 17:12   ` Eli Zaretskii

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83imnatol1.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=dgutov@yandex.ru \
    --cc=emacs-devel@gnu.org \
    --cc=joaotavora@gmail.com \
    --cc=yyoncho@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).