From: Ihor Radchenko <yantar92@posteo.net>
To: Daniel Ortmann <daniel.ortmann@oracle.com>
Cc: emacs-orgmode@gnu.org
Subject: 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: Wed, 19 Oct 2022 06:43:21 +0000 [thread overview]
Message-ID: <87a65scnzq.fsf@localhost> (raw)
In-Reply-To: <1db2468c-a18a-c2ce-de7e-8161919c4cca@oracle.com>
Daniel Ortmann <daniel.ortmann@oracle.com> 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 'R' in the daily agenda took a long time.
>
> I ran profile-start and then pressed R.
> Here are the cpu and memory reports.
> The memory report seems odd to me.
> Thoughts?
>
> 19250 58% + ...
> 13660 41% + command-execute
> 35 0% + timer-event-handler
>
> 3,754,109,912 99% + command-execute
> 168,717 0% + timer-event-handler
> 19,138 0% + redisplay_internal (C function)
> 0 0% ...
Thanks for reporting.
Could you please run the profiler again and then save the reports to
file using M-x profiler-report-write-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-10-19 6:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-18 21:33 [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/)] Daniel Ortmann
2022-10-19 6:43 ` Ihor Radchenko [this message]
2022-10-19 14:29 ` [External] : " Daniel Ortmann
2022-10-20 4:56 ` Ihor Radchenko
2022-10-20 5:03 ` Daniel Ortmann
2022-10-20 5:37 ` 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=87a65scnzq.fsf@localhost \
--to=yantar92@posteo.net \
--cc=daniel.ortmann@oracle.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).