From: Ihor Radchenko <yantar92@gmail.com>
To: numbchild@gmail.com
Cc: Org Mode <emacs-orgmode@gnu.org>
Subject: Re: [PERFORMANCE] Why some org code is so deep invoked?
Date: Fri, 12 Aug 2022 09:51:01 +0800 [thread overview]
Message-ID: <87o7wq8c1m.fsf@localhost> (raw)
In-Reply-To: <62f5a905.c80a0220.1f07b.ffaeSMTPIN_ADDED_BROKEN@mx.google.com>
"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?
I do not see much issue with deep nesting of the code.
--
Ihor Radchenko,
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 parent reply other threads:[~2022-08-12 1:50 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 ` Ihor Radchenko [this message]
2022-08-12 12:14 ` [PERFORMANCE] Why some org code is so deep invoked? Christopher M. Miles
[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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87o7wq8c1m.fsf@localhost \
--to=yantar92@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=numbchild@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.