unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: chenbin.sh@gmail.com, 55729@debbugs.gnu.org
Subject: bug#55729: 27.1; Emacs 28.1 `string-match' is five times slower than Emacs 27.1
Date: Mon, 30 May 2022 18:58:17 +0300	[thread overview]
Message-ID: <83bkvfj9ly.fsf@gnu.org> (raw)
In-Reply-To: <87k0a3vyyh.fsf@gnus.org> (message from Lars Ingebrigtsen on Mon,  30 May 2022 17:09:58 +0200)

> Resent-From: Lars Ingebrigtsen <larsi@gnus.org>
> Original-Sender: "Debbugs-submit" <debbugs-submit-bounces@debbugs.gnu.org>
> Resent-CC: bug-gnu-emacs@gnu.org
> Resent-Sender: help-debbugs@gnu.org
> Cc: 55729@debbugs.gnu.org
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Date: Mon, 30 May 2022 17:09:58 +0200
> 
> Chen Bin <chenbin.sh@gmail.com> writes:
> 
> > Using same machine, same emacs setup, 28 is alwasy much slower than 27.
> 
> How much slower?
> 
> I tried your test, and the results were within a few percentages of each
> other in 27.1 and 28.1.

With a 3GB file being inserted non-literally, there could be factors
at work here that are entirely unrelated to processing speed.  The
implementation of string-match basically didn't change between Emacs
27 and Emacs 28, AFAICT.





  parent reply	other threads:[~2022-05-30 15:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-30 14:45 bug#55729: 27.1; Emacs 28.1 `string-match' is five times slower than Emacs 27.1 Chen Bin
2022-05-30 15:01 ` Ihor Radchenko
2022-05-30 15:09 ` Lars Ingebrigtsen
2022-05-30 15:10   ` Lars Ingebrigtsen
2022-05-30 15:58   ` Eli Zaretskii [this message]
2022-05-30 16:03     ` Eli Zaretskii
2022-05-31  1:04 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-05-31  2:25   ` 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=83bkvfj9ly.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=55729@debbugs.gnu.org \
    --cc=chenbin.sh@gmail.com \
    --cc=larsi@gnus.org \
    /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).