emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
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 11:53:21 +0000	[thread overview]
Message-ID: <87h6y7h1la.fsf@localhost> (raw)
In-Reply-To: <5DC9610E-5849-4C54-A32B-C8C7A1106012@gmail.com>

Mark Barton <mbarton98@gmail.com> writes:

> FYI here is how reducing that number helped with my clocktable updates in the order I tested each value.
> *** org-element--cache-self-verify-frequency 0.01 
> update takes 1:18 (minutes : seconds)
> *** org-element--cache-self-verify-frequency 0.005
> update takes 0:48
> *** org-element--cache-self-verify-frequency 0.002
> update takes 0:28
> *** org-element--cache-self-verify-frequency 0.001
> update takes 0:19
> *** org-element--cache-self-verify-frequency 0.0005
> update takes 0:20
> *** org-element--cache-self-verify-frequency 0.03 (default value)
> update takes 3:29

Thanks for the data!
What about setting org-element--cache-self-verify to nil?
That's what we will do once we finish the test.


-- 
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:[~2022-12-07 11:54 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 [this message]
2022-12-07 18:28         ` Mark Barton
2022-12-07 18:36           ` Ihor Radchenko
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=87h6y7h1la.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).