unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "João Távora" <joaotavora@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Ivan Yonchovski <yyoncho@gmail.com>, emacs-devel <emacs-devel@gnu.org>
Subject: Re: Speedup of functions to en/decode UTF-8 text
Date: Sat, 23 Nov 2019 10:43:08 +0000	[thread overview]
Message-ID: <CALDnm50JAQ3Y8YW2QerM8zVDjOH8Lr9jeBH61nJrmgHPqVvHkw@mail.gmail.com> (raw)
In-Reply-To: <83d0djue4q.fsf@gnu.org>

I work on multiple branches, and I don't always wish to rebase them
on top of master.  Can you say exactly what commit SHA's your
changes consists of, presuming I can cherry-pick them to those
branches?

Thanks,
João



On Sat, Nov 23, 2019 at 9:38 AM Eli Zaretskii <eliz@gnu.org> 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, so I'd welcome speed
> measurements of the current master branch as compared to previous
> versions (yesterday and older) in real-life scenarios, in particular
> in LSP and Eglot.  Please report the results here, and if there are
> some significantly adverse effects of these changes, please report
> them as bugs.
>
> TIA



--
João Távora



  reply	other threads:[~2019-11-23 10:43 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 [this message]
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
     [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=CALDnm50JAQ3Y8YW2QerM8zVDjOH8Lr9jeBH61nJrmgHPqVvHkw@mail.gmail.com \
    --to=joaotavora@gmail.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --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).