From: Ihor Radchenko <yantar92@gmail.com>
To: Greg Coladonato <gcoladon@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [BUG] after update to 9.5, starting org mode results in cache error messages [9.5 (9.5-gd4e192 @ c:/Users/scott/.emacs.d/straight/build/org/)]
Date: Wed, 03 Nov 2021 19:50:25 +0800 [thread overview]
Message-ID: <878ry5e9vi.fsf@localhost> (raw)
In-Reply-To: <CAO09H5uanhCNLwkYH9TS5PMqNf3E=jAKuXcE4nvL0QG2dz7OCA@mail.gmail.com>
Greg Coladonato <gcoladon@gmail.com> writes:
> I uninstalled undo-fu and re-ran the profiler. It takes even longer to save
> org files now. Here's the profiler report now, does it look like helm-M-x
> is
> now the bottleneck?
The profiler does not show anything about saving buffer. I suspect that
you had profiler running for a long time - the statistics appears to be
from a long session, so that saving buffer is insignificant compared to
some command you use frequently (helm search in org buffer?).
To make sure that you are getting profiler statistics just from saving
buffer, you can first run M-x profiler-stop. Only after making sure that
old profiler is not running, you can M-x profiler-start <save buffer>
M-x profiler-report.
Note that you can try to look for the bottleneck yourself: profiler
report buffer works similar to Org buffer - you can hit <TAB> to unfold
the call-tree and reveal more about slow commands.
Best,
Ihor
next prev parent reply other threads:[~2021-11-03 11:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-31 19:26 [BUG] after update to 9.5, starting org mode results in cache error messages [9.5 (9.5-gd4e192 @ c:/Users/scott/.emacs.d/straight/build/org/)] Greg Coladonato
2021-11-01 12:42 ` Ihor Radchenko
2021-11-02 3:25 ` Greg Coladonato
2021-11-02 4:05 ` Ihor Radchenko
2021-11-02 4:33 ` Greg Coladonato
2021-11-02 5:26 ` Ihor Radchenko
2021-11-02 23:06 ` Greg Coladonato
2021-11-03 11:50 ` Ihor Radchenko [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-10-31 3:19 Scott Otterson
2021-10-31 3:53 ` 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=878ry5e9vi.fsf@localhost \
--to=yantar92@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=gcoladon@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).