emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: William Denton <william@williamdenton.org>
To: Emacs Org mode mailing list <emacs-orgmode@gnu.org>
Subject: Re: Things got very slow: profiler output
Date: Sat, 09 Mar 2024 19:27:55 +0000	[thread overview]
Message-ID: <C4Xlqe9US_LJDSR2L4RCKQqelfsO2mkC4HR4VBl1psAN8spB0BDymN6OSdhtXAFCRrXVi4Uov2nArtGw0pzPY5wFYBknwHur2QvMa0eXWq4=@williamdenton.org> (raw)
In-Reply-To: <Id86m1jys_E7KMxsrsMh7I4t1GYcelPnId5-5dizCu5_kVqy_Tlf1fmqMeuYGIJgeWgC2LTAook891D-2L8Xu4NmjvhtSI6KgKPRklbd-OU=@williamdenton.org>

On Thursday, March 7th, 2024 at 11:12, William Denton <william@williamdenton.org> wrote:

> I recompiled Emacs and Org last night and closed all my buffers except for two medium-sized ones, neither with any LaTeX in them. I restarted and spent a minute or two with one buffer, closing and expanding headings, and just moving around without typing, and it quickly slowed down. When I did do a bit of typing it was very laggy (and will only get worse). The profiler said this:
> 
> 44032 66% - redisplay_internal (C function)
> 42619 63% - jit-lock-function
> 42603 63% - jit-lock-fontify-now
> 42551 63% - jit-lock--run-functions
> 42547 63% - run-hook-wrapped
> 42543 63% - #<compiled 0x1badbc188025c93f>
> 
> 42535 63% - font-lock-fontify-region
> 42531 63% - font-lock-default-fontify-region
> 41987 62% - font-lock-fontify-keywords-region
> 40255 60% - org-do-latex-and-related
> 40243 60% re-search-forward
> 12 0% org-string-nw-p
> 1224 1% + org-activate-folds
> 156 0% re-search-forward
> ...
> 
> I'm happy to try anything else ...

I spent a while with git bisect this afternoon and the problem (for me) started here:

commit 5d186b499dde97f59a91dc11f4c4a15113d29f4d
Author: Ihor Radchenko <yantar92@posteo.net>
Date:   Sun Feb 25 11:42:44 2024 +0300

    org-fold: Refactor fontifying newlines after folds

That seems to fit with some of what the profiling showed, in that it's about font-locking, though why LaTeX is mentioned is beyond me.  When I was going through the bisect process I wasn't testing on files with LaTeX, I was expanding and folding some I regularly use that have some code blocks and tables with a few hundred lines.

My Lisp isn't good enough to see why this commit might have changed behaviour.  A couple of people had slowness caused by a spell-checker that was easily fixed ... has no one else seen a problem dating back to late February?  Ihor, does this suggest anything to you?  Is there anything else I could try?

Bill

--
William Denton
https://www.miskatonic.org/
Librarian, artist and licensed private investigator.
Toronto, Canada




  parent reply	other threads:[~2024-03-09 19:33 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-29  5:13 Things got very slow: profiler output William Denton
2024-02-29  9:21 ` Bruno Barbier
2024-02-29  9:28   ` Ihor Radchenko
     [not found] ` <notmuch-sha1-998a6a574db756b51dbdd759ff59b5174d99c7f1>
2024-02-29  9:25   ` Bruno Barbier
2024-03-07 16:12     ` William Denton
2024-03-07 17:42       ` Bruno Barbier
2024-03-09 19:27       ` William Denton [this message]
2024-03-12 12:43         ` Ihor Radchenko
2024-03-13 23:19           ` Bruno Cardoso
2024-03-14  1:17             ` William Denton
2024-03-14  7:34               ` Gerard Vermeulen
2024-03-14 10:27                 ` Bruno Cardoso
2024-03-14 10:22               ` Bruno Cardoso
2024-03-14 21:23             ` Ihor Radchenko
2024-03-15  1:09               ` Bruno Cardoso
2024-03-15 14:24                 ` Ihor Radchenko
2024-03-15 16:33                   ` Bruno Cardoso
2024-03-15 17:18                     ` Ihor Radchenko
2024-03-15 17:49                       ` Bruno Cardoso
2024-03-16  8:56                         ` Ihor Radchenko
2024-03-16 13:31                           ` Bruno Cardoso
2024-03-16 15:56                             ` Ihor Radchenko
2024-03-16 18:39                               ` William Denton
2024-03-16 18:56                                 ` Ihor Radchenko
2024-03-17 18:59                                   ` William Denton
2024-03-17 19:33                                     ` Ihor Radchenko
2024-03-16 20:21                               ` Bruno Cardoso
2024-03-16 21:14                                 ` Ihor Radchenko
2024-03-17 13:02                                   ` Bruno Cardoso
2024-03-17 14:19                                     ` Ihor Radchenko

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.orgmode.org/

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

  git send-email \
    --in-reply-to='C4Xlqe9US_LJDSR2L4RCKQqelfsO2mkC4HR4VBl1psAN8spB0BDymN6OSdhtXAFCRrXVi4Uov2nArtGw0pzPY5wFYBknwHur2QvMa0eXWq4=@williamdenton.org' \
    --to=william@williamdenton.org \
    --cc=emacs-orgmode@gnu.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/org-mode.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).