From: Daniel Ortmann <daniel.ortmann@oracle.com>
To: Eli Qian <eli.q.qian@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [External] : Re: Clocking in is pretty slow in version 9.6 when the item has a large
Date: Sun, 4 Dec 2022 11:59:34 -0600 [thread overview]
Message-ID: <fe690d0f-42e3-d0bc-1aab-fce100eeb3d1@oracle.com> (raw)
In-Reply-To: <87a643f4ng.fsf@localhost>
[-- Attachment #1: Type: text/plain, Size: 561 bytes --]
Eli,
I also had performance issues after the logbook was switched to true
parsing instead of regular expressions. In my case, I had logbook
entries going back to 2012!
After I cleared out the excess entries the performance jumped back up.
https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=3790bf8ea1d070055a989f0b9587948e07877977
On 12/4/22 11:41, Ihor Radchenko wrote:
> Eli Qian <eli.q.qian@gmail.com> writes:
>
>> Any idea about speeding up clocking in?
> Try reducing `org-element--cache-self-verify-frequency' to a smaller
> number.
>
[-- Attachment #2: [External] : Re: [BUG] recent slow down in agenda's clock table report (and with first clock-in) [9.6-pre (release_9.5.5-995-g4b9aef @ /home/dortmann/src/git-org-mode/lisp/)].eml --]
[-- Type: message/rfc822, Size: 1473 bytes --]
From: Daniel Ortmann <daniel.ortmann@oracle.com>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: emacs-orgmode@gnu.org
Subject: Re: [External] : Re: [BUG] recent slow down in agenda's clock table report (and with first clock-in) [9.6-pre (release_9.5.5-995-g4b9aef @ /home/dortmann/src/git-org-mode/lisp/)]
Date: Thu, 20 Oct 2022 11:21:19 -0500
Message-ID: <c07b9f70-d80a-377f-e9ce-c2e32373bc8d@oracle.com>
Works perfectly after cleaning out old time log entries going back to
2013. :-)
On 10/20/22 00:37, Ihor Radchenko wrote:
> Daniel Ortmann <daniel.ortmann@oracle.com> writes:
>
>> (The performance drop was sudden and steep, by the way.)
> It is because clocking now calls Org parser API.
> https://urldefense.com/v3/__https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=3790bf8ea1d070055a989f0b9587948e07877977__;!!ACWV5N9M2RV99hQ!KgwLbNpmmeNRH40ZJBT24H5ehmytyzRmS_wXhRSXlz7b-jzilorwtWKuAF0iQwTkP4UT779uIe4jNXhYh7W-$
>
next prev parent reply other threads:[~2022-12-04 18:00 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 ` Daniel Ortmann [this message]
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
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=fe690d0f-42e3-d0bc-1aab-fce100eeb3d1@oracle.com \
--to=daniel.ortmann@oracle.com \
--cc=eli.q.qian@gmail.com \
--cc=emacs-orgmode@gnu.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/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).