From: Ihor Radchenko <yantar92@posteo.net>
To: Mark Barton <mbarton98@gmail.com>
Cc: Eli Qian <eli.q.qian@gmail.com>, emacs-orgmode@gnu.org
Subject: Re: Clocking in is pretty slow in version 9.6 when the item has a large
Date: Wed, 07 Dec 2022 18:36:24 +0000 [thread overview]
Message-ID: <87mt7znjrr.fsf@localhost> (raw)
In-Reply-To: <D89AD26B-0404-4896-B555-3DC0C0F885C6@gmail.com>
Mark Barton <mbarton98@gmail.com> writes:
>> On Dec 7, 2022, at 3:53 AM, Ihor Radchenko <yantar92@posteo.net> wrote:
>>
>> What about setting org-element--cache-self-verify to nil?
>
> (setq org-element--cache-self-verify-frequency nil)
> Update clocktable
> Wrong type argument: number-or-marker-p, nil
>
> Try again but use zero instead of nil...
> (setq org-element--cache-self-verify-frequency 0)
> Updates in 11s.
Sorry, I meant (setq org-element--cache-self-verify nil).
In any case, the time is back to previous, which should be good enough
considering that no optimizations have been made to the clock table
calculation.
If you need it, you may run M-x profiler-start <RET> cpu <RET>, run
clocktable, M-x profiler-report M-x profiler-report-write-profile, and
share the resulting profile.
--
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>
next prev parent reply other threads:[~2022-12-07 18:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-04 12:12 Clocking in is pretty slow in version 9.6 when the item has a large Eli Qian
2022-12-04 17:34 ` Mark Barton
2022-12-04 17:41 ` Ihor Radchenko
2022-12-04 17:59 ` [External] : " Daniel Ortmann
2022-12-04 18:18 ` Ihor Radchenko
2022-12-04 18:40 ` Mark Barton
2022-12-07 11:53 ` Ihor Radchenko
2022-12-07 18:28 ` Mark Barton
2022-12-07 18:36 ` Ihor Radchenko [this message]
2022-12-07 19:27 ` Mark Barton
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=87mt7znjrr.fsf@localhost \
--to=yantar92@posteo.net \
--cc=eli.q.qian@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=mbarton98@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).