From: Ihor Radchenko <yantar92@posteo.net>
To: Karthik Chikmagalur <karthikchikmagalur@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: org-persist-write slowing down kill-buffer
Date: Fri, 19 Apr 2024 12:38:20 +0000 [thread overview]
Message-ID: <87y199cytf.fsf@localhost> (raw)
In-Reply-To: <874jbz9xvl.fsf@gmail.com>
Karthik Chikmagalur <karthikchikmagalur@gmail.com> writes:
> I've been noticing that kill-buffer blocks Emacs for a noticeable
> period when killing org buffers. Here are elp results obtained by
> instrumenting org-persist-* and kill-buffer:
>
> | Function name | Call count | Elapsed time | Average time |
> |-----------------------------------+------------+--------------+--------------|
> | kill-buffer | 38 | 2.5647546329 | 0.0674935429 |
> | org-persist-write-all-buffer | 1 | 2.562779994 | 2.562779994 |
> | org-persist-write-all | 1 | 2.56277329 | 2.56277329 |
> | org-persist-write | 1 | 1.627834788 | 1.627834788 |
> | org-persist--write-elisp-file | 1 | 0.312172392 | 0.312172392 |
> It blocks Emacs for about 3 seconds each time. Any Org file with > 500
> lines causes this behavior.
>
> I've also attached the sampling profiler output from killing an Org
> buffer.
>
> Some facts that might be relevant:
>
> - I'm using the WIP LaTeX preview system fork of Org, but there are no
> LaTeX previews in the Org buffers that I run these tests on. (There
> aren't even any LaTeX fragments.)
>
> - My org-persist-dir is 627MB in size.
What is your (length org-persist--index) ?
Also, it does not look like your `org-element-ast-map' is compiled.
--
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>
prev parent reply other threads:[~2024-04-19 12:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-18 3:02 org-persist-write slowing down kill-buffer Karthik Chikmagalur
2024-04-19 12:38 ` Ihor Radchenko [this message]
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=87y199cytf.fsf@localhost \
--to=yantar92@posteo.net \
--cc=emacs-orgmode@gnu.org \
--cc=karthikchikmagalur@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/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).