Daniel Ortmann writes:
> (The performance drop was sudden and steep, by the way.)
It is because clocking now calls Org parser API.
https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=3790bf8ea1d070055a989f0b9587948e07877977
--
Ihor Radchenko // yantar92,
Org mode contributor,
Thank you! I will take one or more of those steps.
(The performance drop was sudden and steep, by the way.)
On 10/19/22 23:56, Ihor Radchenko wrote:
Daniel Ortmann writes:
Here you go.
Thanks!
It looks like you have some task with giant years-worth logbook drawer.
You can try to reduce
Daniel Ortmann writes:
> Here you go.
Thanks!
It looks like you have some task with giant years-worth logbook drawer.
You can try to reduce org-element--cache-self-verify-frequency or even
set org-element--cache-self-verify to nil. The latter should be safe if
you haven't seen any Org mode
Daniel Ortmann writes:
> Sometime during the past week I have been surprised by a sudden jump in
> load time when clocking into the first task in the agenda. Today, while
> tracking down that performance change, the problem "disappeared"! The
> first clockin behaved normally.
>
> But! Pressing
Remember to cover the basics, that is, what you expected to happen and
what in fact did happen. You don't know how to make a good report? See
https://orgmode.org/manual/Feedback.html#Feedback
Your bug report will be posted to the Org mailing list.
