unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Björn Bidar" <bjorn.bidar@thaodan.de>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: Eli Zaretskii <eliz@gnu.org>,
	 monnier@iro.umontreal.ca, mattiase@acm.org,
	 arstoffel@gmail.com,  eller.helmut@gmail.com,
	dmcc2@hypnicjerk.ai,  pipcet@protonmail.com,
	 emacs-devel@gnu.org, acorallo@gnu.org,  stefankangas@gmail.com
Subject: Re: [PATCH] add compiled regexp primitive lisp object
Date: Mon, 23 Dec 2024 15:38:12 +0200	[thread overview]
Message-ID: <36450.1531164692$1734961130@news.gmane.org> (raw)
In-Reply-To: <87r05zlas8.fsf@localhost> (Ihor Radchenko's message of "Sun, 22 Dec 2024 20:31:35 +0000")

Ihor Radchenko <yantar92@posteo.net> writes:

> Eli Zaretskii <eliz@gnu.org> writes:
>
>>> >> See https://debbugs.gnu.org/cgi/bugreport.cgi?bug=63225
>>> >> TL;DR: Compiling regexps can take a significant fraction of time when
>>> >> parsing Org documents.
>>> >
>>> > Which fraction?
>>> 
>>> Close to 10%. See the very first message.
>>
>> That's almost negligible, IMO.
>
> It is 2 seconds extra in my tests.
> Also, it is ~20% of all the time taken by regexp matching.
> I would not call it negligible.

Also 10% or 20% percent the effect such an improvement becomes more
significant the bigger the data is or the slower the computer is Emacs
runs on.

Org-Mode files can become quite big, other files possibly too.



  reply	other threads:[~2024-12-23 13:38 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-30  5:08 [PATCH] add compiled regexp primitive lisp object Danny McClanahan
2024-07-30 13:02 ` Philip Kaludercic
2024-07-31 22:33   ` dmcc2
2024-08-01  1:04 ` Pip Cet
2024-08-04 23:38   ` Danny McClanahan
2024-08-05  3:47     ` dmcc2
2024-08-05  4:39   ` Danny McClanahan
2024-08-05  7:15     ` Danny McClanahan
2024-08-05 17:55     ` Pip Cet
2024-08-06 15:15       ` Danny McClanahan
2024-08-06 15:57         ` Eli Zaretskii
2024-08-07  4:28           ` Danny McClanahan
2024-08-06 18:18         ` Pip Cet
2024-08-06 18:38           ` Eli Zaretskii
2024-08-07  4:23             ` Danny McClanahan
2024-08-07 12:00               ` Eli Zaretskii
2024-08-07 12:43                 ` Helmut Eller
2024-08-07 13:40                   ` Augusto Stoffel
2024-08-07 15:23                     ` Danny McClanahan
2024-08-14  1:32                     ` Stefan Monnier
2024-11-26 18:05                       ` Danny McClanahan
2024-11-26 18:50                         ` Danny McClanahan
2024-12-08 15:24                         ` Danny McClanahan
2024-12-09 15:12                           ` Stefan Monnier
2024-12-09 15:13                             ` Stefan Monnier
2024-12-22 19:14                       ` Ihor Radchenko
2024-12-22 19:24                         ` Eli Zaretskii
2024-12-22 20:02                           ` Ihor Radchenko
2024-12-22 20:20                             ` Eli Zaretskii
2024-12-22 20:31                               ` Ihor Radchenko
2024-12-23 13:38                                 ` Björn Bidar [this message]
     [not found]                                 ` <8634ie60jd.fsf@gnu.org>
2024-12-23 16:33                                   ` Ihor Radchenko
2024-12-23 16:49                                     ` Eli Zaretskii
2024-12-23 17:10                                       ` Ihor Radchenko
2024-08-07 15:02                 ` Danny McClanahan
2024-08-07 15:23                   ` Eli Zaretskii
2024-08-14  1:25               ` Stefan Monnier
2024-08-07  7:59           ` Danny McClanahan
2024-08-06 12:08     ` Eli Zaretskii
2024-08-01  8:30 ` Andrea Corallo
2024-08-01 10:06   ` Gerd Möllmann
2024-08-06 13:47   ` Danny McClanahan
2024-08-06 13:57     ` Danny McClanahan
2024-08-07  7:21     ` Andrea Corallo
2024-08-07  8:27       ` Danny McClanahan

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='36450.1531164692$1734961130@news.gmane.org' \
    --to=bjorn.bidar@thaodan.de \
    --cc=acorallo@gnu.org \
    --cc=arstoffel@gmail.com \
    --cc=dmcc2@hypnicjerk.ai \
    --cc=eliz@gnu.org \
    --cc=eller.helmut@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=mattiase@acm.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=pipcet@protonmail.com \
    --cc=stefankangas@gmail.com \
    --cc=yantar92@posteo.net \
    /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).