emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Christopher M. Miles" <numbchild@gmail.com>
To: Ihor Radchenko <yantar92@gmail.com>
Cc: numbchild@gmail.com, Org Mode <emacs-orgmode@gnu.org>
Subject: Re: [PERFORMANCE] Why some org code is so deep invoked?
Date: Fri, 12 Aug 2022 20:14:56 +0800	[thread overview]
Message-ID: <m2r11lr6sy.fsf@numbchild@gmail.com> (raw)
In-Reply-To: <87o7wq8c1m.fsf@localhost>

[-- Attachment #1: Type: text/plain, Size: 1512 bytes --]


Ihor Radchenko <yantar92@gmail.com> writes:

> "Christopher M. Miles" <numbchild@gmail.com> writes:
>
>> When I profiling Org Agenda generation, I found that org code is deeply invoked in Emacs profiler report.
>>
>> My Question:
>>
>> - What reason caused this situation?
>> - Can Org Mode optimize those deeply invoked code?
>
> Could you please clarify what exactly is your problem?
> Is agenda generation slow?

From the profiler report, you can see that Agenda is slow on clock table
generation because I have ~org-agenda-start-with-clockreport-mode~
enabled. And this deep code invocation is from it too. It's about 5
seconds to generate the org-agenda clock table. Actually I can tolerate
this time, Just found this performance issue when profiling and curious
to ask this question.

> I do not see much issue with deep nesting of the code.

Is this deep nested code normal in Emacs Lisp?

Usually (based on my less than 20 times profiling experience), Emacs
wouldn't have deeper code than 40 levels. But my attachment profiler
report has more than 100 levels.

If this is normal and fine, It's OK. I repeat, I ask this question for
curious purpose which want to get an answer for not important question.

-- 

[ stardiviner ]
I try to make every word tell the meaning that I want to express without misunderstanding.

Blog: https://stardiviner.github.io/
IRC(libera.chat, freenode): stardiviner, Matrix: stardiviner
GPG: F09F650D7D674819892591401B5DF1C95AE89AC3

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

  reply	other threads:[~2022-08-12 12:22 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <62f5a905.c80a0220.1f07b.ffaeSMTPIN_ADDED_BROKEN@mx.google.com>
2022-08-12  1:51 ` [PERFORMANCE] Why some org code is so deep invoked? Ihor Radchenko
2022-08-12 12:14   ` Christopher M. Miles [this message]
     [not found]   ` <62f64617.050a0220.b0be5.b717SMTPIN_ADDED_BROKEN@mx.google.com>
2022-08-12 12:51     ` Bill Burdick
2022-08-12 14:16       ` Christopher M. Miles
     [not found]   ` <62f645de.050a0220.ff872.76ffSMTPIN_ADDED_BROKEN@mx.google.com>
2022-08-12 13:12     ` Ihor Radchenko
2022-08-12 14:12       ` Christopher M. Miles
     [not found]       ` <62f660a5.1f0a0220.73d8b.c78bSMTPIN_ADDED_BROKEN@mx.google.com>
2022-08-12 14:23         ` Ihor Radchenko
2022-08-12 14:30       ` Christopher M. Miles
     [not found]       ` <62f66552.050a0220.ed346.ac05SMTPIN_ADDED_BROKEN@mx.google.com>
2022-08-13  6:50         ` Ihor Radchenko
2022-08-13  8:10           ` Christopher M. Miles
     [not found]           ` <62f75d06.c80a0220.460f4.cc42SMTPIN_ADDED_BROKEN@mx.google.com>
2022-08-13  8:48             ` Ihor Radchenko
2022-08-13 13:48               ` Christopher M. Miles
2022-08-12  0:26 Christopher M. Miles

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=m2r11lr6sy.fsf@numbchild@gmail.com \
    --to=numbchild@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=yantar92@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).