unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@posteo.net>
To: Yuchen Pei <id@ypei.org>
Cc: emacs-devel@gnu.org
Subject: Re: 29.0.91 756244c696 Saving large org file can be slow with time-stamp before-save-hook
Date: Sun, 04 Jun 2023 06:23:45 +0000	[thread overview]
Message-ID: <87pm6blp8u.fsf@localhost> (raw)
In-Reply-To: <87ilc4ok4d.fsf@ypei.org>

Yuchen Pei <id@ypei.org> writes:

> emacs-29 756244c69638bc3562d8cd2c1aa126216e99fb29 build.
>
> Not sure how to reprod with something from scratch. But here are the
> steps to reprod with a large "organic" org file with emacs -Q
>
> - (add-hook 'before-save-hook 'time-stamp)
> - Open a very large org file with a "Time-stamp:" at the beginning of the
>   file
> - (setq org-refile-use-cache t)
> - (setq org-refile-use-outline-path t)
> - (setq org-refile-targets '((org-agenda-files :maxlevel . 5)))
> - (setq org-goto-interface 'outline-path-completion)
> - M-x org-goto, which triggers `org-refile-get-targets`, wait for it to
>   finish

Potentially a duplicate of https://debbugs.gnu.org/cgi/bugreport.cgi?bug=58558
`org-refile-get-targets' creates a bunch of markers in buffer and in the
discussion of bug#58558 we have found that
`parse-sexp-lookup-properties' set to non-nil dramatically slows down
searching in buffer, with slowdown scaling with the number of markers.
There is also a fix.

Yuchen, may you try to set `parse-sexp-lookup-properties' locally to nil
in your large Org buffer? If it helps, that's it.

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>



  reply	other threads:[~2023-06-04  6:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-03 11:33 29.0.91 756244c696 Saving large org file can be slow with time-stamp before-save-hook Yuchen Pei
2023-06-04  6:23 ` Ihor Radchenko [this message]
2023-06-04  6:45   ` Yuchen Pei
2023-06-12 13:10     ` Ihor Radchenko
2023-06-12 13:28       ` Yuchen Pei
2023-06-12 18:50         ` Ihor Radchenko
2023-06-13 12:30           ` Yuchen Pei
2023-06-13 12:54             ` 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.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=87pm6blp8u.fsf@localhost \
    --to=yantar92@posteo.net \
    --cc=emacs-devel@gnu.org \
    --cc=id@ypei.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).